CVE-2026-46417

MediumCVSS 6.1

Published: 22/06/2026(UTC)Updated: 15/07/2026(UTC)Translated: 16/07/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.22%

13th percentile - higher than 13% of all known CVEs

Summary

In Angular prior to versions 22.0.0-next.12, 21.2.13, 20.3.21, and 19.2.22, an SSRF vulnerability exists in @angular/platform-server. The SSR engine mishandles absolute-form URLs, allowing an attacker to manipulate the hostname and redirect HttpClient requests to an attacker-controlled server.

Risk Assessment

An attacker can exploit this to access internal APIs or metadata services, leading to sensitive data exposure or further attacks within the internal network.

Recommendation

Immediately update Angular to version 22.0.0-next.12, 21.2.13, 20.3.21, or 19.2.22 depending on your branch. After updating, verify SSR configuration and restrict access to internal resources.

Other vulnerabilities in @angular/platform-server

CVE-2026-50168High
A vulnerability in the @angular/platform-server package allows attackers to bypass host allowlist constraints and direct server-side outgoing requests to arbitrary external endpoints. This issue arises from a parser differential between the strict WHATWG URL parser and the lenient Domino parser, leading to an SSRF attack.

Original NVD description (English source)

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.