CVE-2026-44437
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| npm | @angular/ssr | >=22.0.0-next.0,<22.0.0-next.7 | 22.0.0-next.7 |
| npm | @angular/ssr | >=21.0.0-next.0,<21.2.9 | 21.2.9 |
| npm | @angular/ssr | >=20.0.0-next.0,<20.3.25 | 20.3.25 |
| npm | @angular/ssr | >=19.0.0-next.0,<19.2.25 | 19.2.25 |
| NPM | @angular/ssr | >= 19.0.0-next.0, < 19.2.25 | 19.2.25 |
| NPM | @angular/ssr | >= 20.0.0-next.0, < 20.3.25 | 20.3.25 |
| NPM | @angular/ssr | >= 21.0.0-next.0, < 21.2.9 | 21.2.9 |
| NPM | @angular/ssr | >= 22.0.0-next.0, < 22.0.0-next.7 | 22.0.0-next.7 |
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| angular | angular_cli | {"startIncluding":"19.0.0","endExcluding":"19.2.25"} | 19.2.25 |
| angular | angular_cli | {"startIncluding":"20.0.0","endExcluding":"20.3.25"} | 20.3.25 |
| angular | angular_cli | {"startIncluding":"21.0.0","endExcluding":"21.2.9"} | 21.2.9 |
| angular | angular_cli | 22.0.0 | |
References
- https://github.com/angular/angular-cli/pull/33031
- https://github.com/angular/angular-cli/security/advisories/GHSA-69xr-m8h6-h664
- https://nvd.nist.gov/vuln/detail/CVE-2026-44437
- https://angular.dev/best-practices/security#configuring-trusted-proxy-headers
- https://github.com/angular/angular-cli
- https://github.com/advisories/GHSA-69xr-m8h6-h664
CWEs
CWE-22 CWE-601
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.