CVE-2026-33397: CWE-601: URL Redirection to Untrusted Site ('Open Redirect') in angular angular-cli
The Angular SSR is a server-rise rendering tool for Angular applications. Versions on the 22.x branch prior to 22.0.0-next.2, the 21.x branch prior to 21.2.3, and the 20.x branch prior to 20.3.21 have an Open Redirect vulnerability in `@angular/ssr` due to an incomplete fix for CVE-2026-27738. While the original fix successfully blocked multiple leading slashes (e.g., `///`), the internal validation logic fails to account for a single backslash (`\`) bypass. When an Angular SSR application is deployed behind a proxy that passes the `X-Forwarded-Prefix` header, an attacker provides a value starting with a single backslash, the internal validation failed to flag the single backslash as invalid, the application prepends a leading forward slash, resulting in a `Location` header containing the URL, and modern browsers interpret the `/\` sequence as `//`, treating it as a protocol-relative URL and redirecting the user to the attacker-controlled domain. Furthermore, the response lacks the `Vary: X-Forwarded-Prefix` header, allowing the malicious redirect to be stored in intermediate caches (Web Cache Poisoning). Versions 22.0.0-next.2, 21.2.3, and 20.3.21 contain a patch. Until the patch is applied, developers should sanitize the `X-Forwarded-Prefix` header in their `server.ts` before the Angular engine processes the request.
AI Analysis
Technical Summary
Angular SSR versions on the 22.x branch before 22.0.0-next.2, 21.x before 21.2.3, and 20.x before 20.3.21 contain an Open Redirect vulnerability (CWE-601) due to incomplete validation of the X-Forwarded-Prefix header. The original fix for CVE-2026-27738 blocked multiple leading slashes but did not account for a single backslash, which browsers interpret as a protocol-relative URL, enabling redirection to attacker-controlled sites. Additionally, the lack of a Vary: X-Forwarded-Prefix header allows malicious redirects to be cached by intermediaries. The vulnerability is fixed in versions 22.0.0-next.2, 21.2.3, and 20.3.21.
Potential Impact
An attacker can exploit this vulnerability to redirect users of Angular SSR applications to malicious websites by manipulating the X-Forwarded-Prefix header. This can lead to phishing or other social engineering attacks. The absence of the Vary header also enables web cache poisoning, potentially affecting multiple users. The CVSS score is 6.9 (medium severity), indicating a moderate risk without requiring user interaction or privileges.
Mitigation Recommendations
A patch is available in Angular SSR versions 22.0.0-next.2, 21.2.3, and 20.3.21. Users should upgrade to these or later versions to remediate the vulnerability. Until patched, developers should sanitize the X-Forwarded-Prefix header in their server.ts files before processing requests with Angular SSR. This manual mitigation helps prevent exploitation by filtering or validating the header value.
CVE-2026-33397: CWE-601: URL Redirection to Untrusted Site ('Open Redirect') in angular angular-cli
Description
The Angular SSR is a server-rise rendering tool for Angular applications. Versions on the 22.x branch prior to 22.0.0-next.2, the 21.x branch prior to 21.2.3, and the 20.x branch prior to 20.3.21 have an Open Redirect vulnerability in `@angular/ssr` due to an incomplete fix for CVE-2026-27738. While the original fix successfully blocked multiple leading slashes (e.g., `///`), the internal validation logic fails to account for a single backslash (`\`) bypass. When an Angular SSR application is deployed behind a proxy that passes the `X-Forwarded-Prefix` header, an attacker provides a value starting with a single backslash, the internal validation failed to flag the single backslash as invalid, the application prepends a leading forward slash, resulting in a `Location` header containing the URL, and modern browsers interpret the `/\` sequence as `//`, treating it as a protocol-relative URL and redirecting the user to the attacker-controlled domain. Furthermore, the response lacks the `Vary: X-Forwarded-Prefix` header, allowing the malicious redirect to be stored in intermediate caches (Web Cache Poisoning). Versions 22.0.0-next.2, 21.2.3, and 20.3.21 contain a patch. Until the patch is applied, developers should sanitize the `X-Forwarded-Prefix` header in their `server.ts` before the Angular engine processes the request.
CVSS v4.0
Score 6.9medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Angular SSR versions on the 22.x branch before 22.0.0-next.2, 21.x before 21.2.3, and 20.x before 20.3.21 contain an Open Redirect vulnerability (CWE-601) due to incomplete validation of the X-Forwarded-Prefix header. The original fix for CVE-2026-27738 blocked multiple leading slashes but did not account for a single backslash, which browsers interpret as a protocol-relative URL, enabling redirection to attacker-controlled sites. Additionally, the lack of a Vary: X-Forwarded-Prefix header allows malicious redirects to be cached by intermediaries. The vulnerability is fixed in versions 22.0.0-next.2, 21.2.3, and 20.3.21.
Potential Impact
An attacker can exploit this vulnerability to redirect users of Angular SSR applications to malicious websites by manipulating the X-Forwarded-Prefix header. This can lead to phishing or other social engineering attacks. The absence of the Vary header also enables web cache poisoning, potentially affecting multiple users. The CVSS score is 6.9 (medium severity), indicating a moderate risk without requiring user interaction or privileges.
Mitigation Recommendations
A patch is available in Angular SSR versions 22.0.0-next.2, 21.2.3, and 20.3.21. Users should upgrade to these or later versions to remediate the vulnerability. Until patched, developers should sanitize the X-Forwarded-Prefix header in their server.ts files before processing requests with Angular SSR. This manual mitigation helps prevent exploitation by filtering or validating the header value.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-19T17:02:34.169Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69c57a7f3c064ed76f9f9d3e
Added to database: 03/26/2026, 18:27:11 UTC
Last enriched: 04/03/2026, 13:07:08 UTC
Last updated: 07/04/2026, 06:33:04 UTC
Views: 226
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.