CVE-2026-44437
CVE-2026-44437 · Angular SSR: Open Redirect and Request Steering via Encoded X-Forwarded-Prefix
This page contains facts from public vulnerability sources. Check the original advisory before updating.
The Angular SSR is a server-rise rendering tool for Angular applications. From 19.0.0-next.0 to before 19.2.25, 20.3.25, 21.2.9, and 22.0.0-next.7, a vulnerability exists in the X-Forwarded-Prefix header processing logic within Angular SSR. The internal validation mechanism fails to properly account for URL-encoded characters, specifically dots (%2e%2e). This allows an attacker to bypass security filters by injecting encoded path traversal sequences that are later decoded and utilized by the application logic. When an Angular SSR application is configured to trust proxy headers and is deployed behind a proxy that forwards the X-Forwarded-Prefix header without prior sanitization, an attacker can provide a payload such as /%2e%2e/evil. This vulnerability is fixed in19.2.25, 20.3.25, 21.2.9, and 22.0.0-next.7.
CVSS 6.9 · Medium · EPSS 0.2% · Fix available
- Published
- Updated
Stack: node
Affected products and versions
angular-cli
- Versions
- >= 22.0.0-next.0, < 22.0.0-next.7: Affected
- >= 21.0.0-next.0, < 21.2.9: Affected
- >= 20.0.0-next.0, < 20.3.25: Affected
- >= 19.0.0-next.0, < 19.2.25: Affected
No fix published
@angular/ssr npm
- Affected ranges
- SEMVER: ≥ 22.0.0-next.0, < 22.0.0-next.7
Update to 22.0.0-next.7
@angular/ssr npm
- Affected ranges
- SEMVER: ≥ 21.0.0-next.0, < 21.2.9
Update to 21.2.9
@angular/ssr npm
- Affected ranges
- SEMVER: ≥ 20.0.0-next.0, < 20.3.25
Update to 20.3.25
@angular/ssr npm
- Affected ranges
- SEMVER: ≥ 19.0.0-next.0, < 19.2.25
Update to 19.2.25