Angular SSR Flaw Enables SSRF via Malformed URLs in Server-Side Rendering
Vulnerability Disclosure · 2 sources · Updated 5mo ago · First seen May 8, 2026

Angular disclosed a server-side request forgery (SSRF) issue in @angular/platform-server that affects applications using Server-Side Rendering. The flaw, tracked as CVE-2026-41423, stems from improper handling of protocol-relative and backslash-based URLs passed from server engines such as Express into Angular rendering functions. A crafted request can cause Angular to treat an attacker-controlled domain as the application's origin, allowing relative HttpClient requests and PlatformLocation.hostname references to resolve to external infrastructure.
The issue can expose internal services, including private APIs and cloud metadata endpoints, and related advisory material also links the bug family to header injection risks in Angular SSR deployments. Angular fixed the vulnerability in versions 19.2.21, 20.3.19, 21.2.9, and 22.0.0-next.8, leaving earlier releases vulnerable where SSR is enabled and untrusted request paths can influence rendering context.


