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

Severity: medium (CVSS 6.1 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.4% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-06-22 · updated 2026-07-15
Weakness: CWE-918

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.

Affected products

angular: through 18.2.14; from 19.0.0 before 19.2.22; from 20.0.0 before 20.3.21; from 21.0.0 before 21.2.13; 22.0.0-next0, 22.0.0-next1, 22.0.0-next10, 22.0.0-next11, 22.0.0-next2, 22.0.0-next3 (+6) — fixed in 19.2.22, 20.3.21, 21.2.13

How to fix

Upgrade to a fixed version: angular 19.2.22, 20.3.21, 21.2.13. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-46417 or the next vulnerability affects your stack