CVE-2026-46417 Angular: SSRF via Hostname Hijacking in @angular/platform-server
Attackers can exploit SSRF in Angular's server-side rendering to redirect internal requests to malicious servers, exposing sensitive data.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-46417?
CVE-2026-46417 is a high-severity server-side request forgery vulnerability in angular, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-next.12, 21.2.13, 20.3.21, and 19.2.22, a Server-Side Request Forgery (SSRF) vulnerability exists in @angular/platform-server. The issue stems from how the server-side rendering (SSR) engine processes the request URL provided to the rendering entry points. When an absolute-form URL (e.g., http://evil.com) is passed to the rendering engine, the internal ServerPlatformLocation can be manipulated into adopting the attacker-controlled domain as the "current" hostname. Consequently, any relative HttpClient requests or PlatformLocation.hostname references are redirected to the attacker controlled server, potentially exposing internal APIs or metadata services. This vulnerability is fixed in 22.0.0-next.12, 21.2.13, 20.3.21, and 19.2.22.
Weakness: CWE-918
Which versions are affected by CVE-2026-46417?
10 open source packages ship an affected version, including @angular/platform-server. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
@angular/platform-server npm | All versions to 18.2.14 | None |
@angular/platform-server npm | All versions to 18.2.14 | None |
@angular/platform-server npm | From 19.0.0-next.0 | 19.2.22 |
@angular/platform-server npm | From 19.0.0-next.0 | 19.2.22 |
@angular/platform-server npm | From 20.0.0-next.0 | 20.3.21 |
@angular/platform-server npm | From 20.0.0-next.0 | 20.3.21 |
4 more packages
@angular/platform-server npm | From 21.0.0-next.0 | 21.2.13 |
@angular/platform-server npm | From 21.0.0-next.0 | 21.2.13 |
@angular/platform-server npm | From 22.0.0-next.0 | 22.0.0-next.12 |
@angular/platform-server npm | From 22.0.0-next.0 | 22.0.0-next.12 |
Products include Angular Angular.
How do I fix CVE-2026-46417?
Upgrade @angular/platform-server to a fixed version for your release line: 19.2.22, 20.3.21, 21.2.13 or 22.0.0-next.12.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-46417 being exploited?
There is no known exploitation of CVE-2026-46417 in the wild and no public exploit code.
Other vulnerabilities in angular
- CVE-2026-68945 Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
- CVE-2026-50168 Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass
- CVE-2026-54266 Angular: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning
- CVE-2026-41423 Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server
- CVE-2026-88056 Angular: SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR
Sources
Also known as CLSA-2026-1781052756, CLSA-2026-1781139159, CLSA-2026-1781139160, CLSA-2026-1781139161, CLSA-2026-1781139164, CLSA-2026-1781139193 and 175 more.