Angular up to 18.2.14/19.2.21/20.3.20/21.2.12 server-side request forgery

Summaryinfo

A vulnerability was found in Angular up to 18.2.14/19.2.21/20.3.20/21.2.12. It has been rated as critical. The affected element is an unknown function. The manipulation leads to server-side request forgery. This vulnerability is referenced as CVE-2026-46417. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Angular up to 18.2.14/19.2.21/20.3.20/21.2.12 and classified as critical. This issue affects an unknown function. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-46417 since 05/13/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 19.2.22, 20.3.21, 21.2.13 or 22.0.0-next.12 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• JavaScript Library

Name

• Angular

Version

• 18.2.0
• 18.2.1
• 18.2.2
• 18.2.3
• 18.2.4
• 18.2.5
• 18.2.6
• 18.2.7
• 18.2.8
• 18.2.9
• 18.2.10
• 18.2.11
• 18.2.12
• 18.2.13
• 18.2.14
• 19.2.0
• 19.2.1
• 19.2.2
• 19.2.3
• 19.2.4
• 19.2.5
• 19.2.6
• 19.2.7
• 19.2.8
• 19.2.9
• 19.2.10
• 19.2.11
• 19.2.12
• 19.2.13
• 19.2.14
• 19.2.15
• 19.2.16
• 19.2.17
• 19.2.18
• 19.2.19
• 19.2.20
• 19.2.21
• 20.3.0
• 20.3.1
• 20.3.2
• 20.3.3
• 20.3.4
• 20.3.5
• 20.3.6
• 20.3.7
• 20.3.8
• 20.3.9
• 20.3.10
• 20.3.11
• 20.3.12
• 20.3.13
• 20.3.14
• 20.3.15
• 20.3.16
• 20.3.17
• 20.3.18
• 20.3.19
• 20.3.20
• 21.2.0
• 21.2.1
• 21.2.2
• 21.2.3
• 21.2.4
• 21.2.5
• 21.2.6
• 21.2.7
• 21.2.8
• 21.2.9
• 21.2.10
• 21.2.11
• 21.2.12

Website

• Product: https://github.com/angular/angular/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion