Angular up to 18.2.14/19.2.22/20.3.21/21.2.14 WHATWG URL Parser origin validation

Summaryinfo

A vulnerability was found in Angular up to 18.2.14/19.2.22/20.3.21/21.2.14. It has been declared as critical. Affected is an unknown function of the component WHATWG URL Parser. The manipulation results in origin validation. This vulnerability is identified as CVE-2026-50168. The attack can be executed remotely. There is not any exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in Angular up to 18.2.14/19.2.22/20.3.21/21.2.14. Affected is some unknown processing of the component WHATWG URL Parser. The manipulation with an unknown input leads to a origin validation vulnerability. CWE is classifying the issue as CWE-346. The product does not properly verify that the source of data or communication is valid. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23, an issue in the @angular/platform-server package allows remote attackers to bypass host allowlist constraints and direct server-side outgoing requests to arbitrary external endpoints. This occurs due to a parser differential between the strict WHATWG URL parser used for allowlist validation and the lenient Domino URL parser used to initialize the server emulated DOM. When a server-side request contains a malformed URL with a double port structure (e.g., http://evil.com:80:80/path), Node's strict URL.canParse(url) logic returns false and skips host check validation entirely. However, the same malformed URL is later accepted and parsed leniently by Domino's internal parser, which resolves the origin to http://evil.com:80. The Angular SSR HTTP request interceptor (relativeUrlsTransformerInterceptorFn) then resolves all relative backend HTTP requests against this adopted origin, executing the SSRF attack. This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-50168 since 06/03/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available.

Upgrading to version 19.2.23, 20.3.22, 21.2.15 or 22.0.0-rc.2 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.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-38293). Once again VulDB remains the best source for 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
• 19.2.22
• 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
• 20.3.21
• 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
• 21.2.13
• 21.2.14

Website

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

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion