# 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. - **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Jun 2026 - **Updated:** 15 Jul 2026 - **Also known as:** CLSA-2026-1781052756, CLSA-2026-1781139159, CLSA-2026-1781139160, CLSA-2026-1781139161, CLSA-2026-1781139164, CLSA-2026-1781139193, CLSA-2026-1781139195, CLSA-2026-1781139200, CLSA-2026-1781139204, CLSA-2026-1781139206, CLSA-2026-1781139207, CLSA-2026-1781139208, CLSA-2026-1792160920, CLSA-2026-1792161155, CLSA-2026-1792161156, CLSA-2026-1792161157, CLSA-2026-1792161158, CLSA-2026-1792161159, CLSA-2026-1792161160, CLSA-2026-1792161161, CLSA-2026-1792161162, CLSA-2026-1792161163, CLSA-2026-1792161165, CLSA-2026-1792161166, CLSA-2026-1792163544, CLSA-2026-1792163545, CLSA-2026-1792163546, CLSA-2026-1792163547, CLSA-2026-1792163548, CLSA-2026-1792163549, CLSA-2026-1792163551, CLSA-2026-1792163552, CLSA-2026-1792163553, CLSA-2026-1792163554, CLSA-2026-1792163555, CLSA-2026-1792163556, CLSA-2026-1792208105, CLSA-2026-1792208106, CLSA-2026-1792208107, CLSA-2026-1792208108, CLSA-2026-1792208460, CLSA-2026-1792208506, CLSA-2026-1792208520, CLSA-2026-1792208530, CLSA-2026-1792208579, CLSA-2026-1792208638, CLSA-2026-1792208639, CLSA-2026-1792208640, CLSA-2026-1792250210, CLSA-2026-1792250211, CLSA-2026-1792250212, CLSA-2026-1792250213, CLSA-2026-1792250480, CLSA-2026-1792250481, CLSA-2026-1792250527, CLSA-2026-1792250539, CLSA-2026-1792250551, CLSA-2026-1792250568, CLSA-2026-1792250600, CLSA-2026-1792250788, CLSA-2026-1792281079, CLSA-2026-1792281080, CLSA-2026-1792281081, CLSA-2026-1792281082, CLSA-2026-1792281083, CLSA-2026-1792281084, CLSA-2026-1792281085, CLSA-2026-1792281086, CLSA-2026-1792281714, CLSA-2026-1792281806, CLSA-2026-1792281819, CLSA-2026-1792281821, CLSA-2026-1792325331, CLSA-2026-1792325332, CLSA-2026-1792325333, CLSA-2026-1792325334, CLSA-2026-1792325937, CLSA-2026-1792325938, CLSA-2026-1792325939, CLSA-2026-1792325940, CLSA-2026-1792326028, CLSA-2026-1792326044, CLSA-2026-1792326067, CLSA-2026-1792326068, CLSA-2026-1792345192, CLSA-2026-1792345193, CLSA-2026-1792345194, CLSA-2026-1792345195, CLSA-2026-1792345196, CLSA-2026-1792345197, CLSA-2026-1792345198, CLSA-2026-1792345643, CLSA-2026-1792345690, CLSA-2026-1792345709, CLSA-2026-1792345725, CLSA-2026-1792345755, CLSA-2026-1792357248, CLSA-2026-1792357249, CLSA-2026-1792357250, CLSA-2026-1792357251, CLSA-2026-1792357252, CLSA-2026-1792357253, CLSA-2026-1792357254, CLSA-2026-1792357255, CLSA-2026-1792357953, CLSA-2026-1792357954, CLSA-2026-1792357955, CLSA-2026-1792357956, CLSA-2026-1792366551, CLSA-2026-1792366552, CLSA-2026-1792366553, CLSA-2026-1792366554, CLSA-2026-1792366555, CLSA-2026-1792366883, CLSA-2026-1792366900, CLSA-2026-1792366901, CLSA-2026-1792366902, CLSA-2026-1792366915, CLSA-2026-1792366925, CLSA-2026-1792367037, CLSA-2026-1792371603, CLSA-2026-1792371604, CLSA-2026-1792371605, CLSA-2026-1792371606, CLSA-2026-1792371607, CLSA-2026-1792372006, CLSA-2026-1792372007, CLSA-2026-1792372008, CLSA-2026-1792372055, CLSA-2026-1792372106, CLSA-2026-1792375708, CLSA-2026-1792375709, CLSA-2026-1792375710, CLSA-2026-1792375711, CLSA-2026-1792375712, CLSA-2026-1792375713, CLSA-2026-1792375714, CLSA-2026-1792376088, CLSA-2026-1792376116, CLSA-2026-1792376148, CLSA-2026-1792376208, CLSA-2026-1792376209, CLSA-2026-1792379969, CLSA-2026-1792379970, CLSA-2026-1792379971, CLSA-2026-1792379972, CLSA-2026-1792380389, CLSA-2026-1792380421, CLSA-2026-1792380422, CLSA-2026-1792380432, CLSA-2026-1792380478, CLSA-2026-1792380479, CLSA-2026-1792380480, CLSA-2026-1792380481, CLSA-2026-1792382596, CLSA-2026-1792382597, CLSA-2026-1792382598, CLSA-2026-1792382911, CLSA-2026-1792382938, CLSA-2026-1792382948, CLSA-2026-1792382964, CLSA-2026-1792382996, CLSA-2026-1792383061, CLSA-2026-1792383189, CLSA-2026-1792383190, CLSA-2026-1792383191, CLSA-2026-1792386073, CLSA-2026-1792386074, CLSA-2026-1792386075, CLSA-2026-1792386076, CLSA-2026-1792386077, CLSA-2026-1792386419, CLSA-2026-1792386420, CLSA-2026-1792386443, CLSA-2026-1792386470, CLSA-2026-1792386518, CLSA-2026-1792386519, CLSA-2026-1792386578, DEBIAN-CVE-2026-46417, GHSA-rfh7-fxqc-q52v, UBUNTU-CVE-2026-46417 ## 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 (Server-Side Request Forgery) ## 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 | Ecosystem | 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 | | `@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: 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. ## 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](https://insights.sbomify.com/CVE-2026-68945/): Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning (high 8.8) - [CVE-2026-50168](https://insights.sbomify.com/CVE-2026-50168/): Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass (high 8.8) - [CVE-2026-54266](https://insights.sbomify.com/CVE-2026-54266/): Angular: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning (high 8.8) - [CVE-2026-41423](https://insights.sbomify.com/CVE-2026-41423/): Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server (high 8.7) - [CVE-2026-88056](https://insights.sbomify.com/CVE-2026-88056/): Angular: SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR (high 8.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-46417 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2026-46417 in the wild and no public exploit code. Affected packages and fixed versions: - @angular/platform-server (npm): affected all versions up to 18.2.14; no fix listed - @angular/platform-server (npm): affected all versions up to 18.2.14; no fix listed - @angular/platform-server (npm): affected from 19.0.0-next.0; fixed in 19.2.22 - @angular/platform-server (npm): affected from 19.0.0-next.0; fixed in 19.2.22 - @angular/platform-server (npm): affected from 20.0.0-next.0; fixed in 20.3.21 - @angular/platform-server (npm): affected from 20.0.0-next.0; fixed in 20.3.21 - @angular/platform-server (npm): affected from 21.0.0-next.0; fixed in 21.2.13 - @angular/platform-server (npm): affected from 21.0.0-next.0; fixed in 21.2.13 - @angular/platform-server (npm): affected from 22.0.0-next.0; fixed in 22.0.0-next.12 - @angular/platform-server (npm): affected from 22.0.0-next.0; fixed in 22.0.0-next.12 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-46417/ (Markdown: https://insights.sbomify.com/CVE-2026-46417/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46417 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46417 - OSV: https://osv.dev/vulnerability/CVE-2026-46417 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-46417/ Summaries are generated and may contain mistakes; the official description above is the record.