Open redirect vulnerabilities allow attackers to craft URLs that appear to lead to legitimate domains but redirect victims to malicious sites. Although not ranked highly in recent OWASP Top 10 lists, open redirects continue to be exploited in phishing campaigns. Analysis of phishing emails collected in early 2026 revealed that over 21% of phishing messages used redirect-based links, including fully open redirects, token-based 'half-open' redirects, and URL shorteners. These redirectors can be part of tracking, advertising, or logout mechanisms and are abused to bypass email scanners and deceive users. Tokens used in some redirect mechanisms, such as those on Google or Bing, are often reusable and long-lived, facilitating repeated abuse. The persistence and variety of redirect abuses highlight the need for organizations to audit and restrict redirect endpoints to reduce phishing risks.

The misuse of open redirect mechanisms in phishing campaigns increases the likelihood that phishing links will appear legitimate to recipients and evade detection by email security tools. This can lead to higher success rates for phishing attacks, potentially resulting in credential theft, unauthorized access, or other malicious outcomes. Although open redirects themselves are not high-impact vulnerabilities, their exploitation in phishing campaigns poses a medium-level threat by facilitating social engineering attacks.

Organizations should audit their applications to identify and eliminate open redirect endpoints where possible. If redirection functionality is necessary, it should be strictly controlled, monitored for abuse, and restricted to trusted destinations. Since no specific patch or vendor advisory is applicable, remediation involves secure coding practices and operational monitoring. There is no indication that this threat is mitigated by vendor fixes or cloud service provider actions. Patch status is not applicable. Defensive measures should focus on reducing exposure to redirect abuse and improving detection of phishing attempts leveraging redirects.