CVE-2026-50168

Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass

HIGH
8.2
CVSS Score
Published: June 22, 2026 at 03:39 PM UTC
Updated: July 9, 2026 at 03:24 PM UTC
1 product affected across 1 vendor@angular

Using angular by angular?

Get instant alerts when new vulnerabilities affect angular - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.2
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≤ 18.2.14v < 19.2.23v < 20.3.22v < 21.2.15v < 22.0.0-rc.219.0.0 ≤ v < 19.2.232.0.0 ≤ v ≤ 18.2.1420.0.0 ≤ v < 20.3.2221.0.0 ≤ v < 21.2.1522.0.0 next022.0.0 next122.0.0 next1022.0.0 next1122.0.0 next1222.0.0 next222.0.0 next322.0.0 next422.0.0 next522.0.0 next622.0.0 next722.0.0 next822.0.0 next922.0.0 rc022.0.0 rc1
Affected range stops below 19.2.23, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.3.22, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.0.0-rc.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

x_refsource_CONFIRMVendor Advisory
Source: cverecord
https://github.com/angular/angular/security/advisories/GHSA-xrxm-cp7j-8xf6
x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/angular/angular/pull/68928

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-346CWE-918

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card