CVE-2026-50168 [High] | Security Bypass in Angular

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-07-01	0.28%	0.19%	-0.09%
2	2026-06-23	0.03%	0.28%	+0.25%
3	2026-06-12	—	0.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-07-01

0.28%

0.19%

-0.09%

2026-06-23

0.03%

0.28%

+0.25%

2026-06-12

—

0.03%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	4.0	HIGH	`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network. Attack complexity (AC:L) Exploitation conditions are straightforward and stable. Attack requirements (AT:N) No additional preconditions are required beyond normal reachability. Privileges required (PR:N) No privileges are required. User interaction (UI:N) No user interaction is required. Vulnerable system confidentiality impact (VC:H) High confidentiality impact on the vulnerable system. Vulnerable system integrity impact (VI:L) Limited integrity impact on the vulnerable system. Vulnerable system availability impact (VA:N) No availability impact on the vulnerable system. Subsequent system confidentiality impact (SC:N) No confidentiality impact on subsequent systems. Subsequent system integrity impact (SI:N) No integrity impact on subsequent systems. Subsequent system availability impact (SA:N) No availability impact on subsequent systems. Exploit maturity (threat) (E:X) Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked). Confidentiality requirement (CR:X) Not defined: insufficient information; scoring treats this like High (worst case). Integrity requirement (IR:X) Not defined: insufficient information; scoring treats this like High (worst case). Availability requirement (AR:X) Not defined: insufficient information; scoring treats this like High (worst case). Modified attack vector (MAV:X) Not defined: scoring uses the Base Attack Vector (AV). Modified attack complexity (MAC:X) Not defined: scoring uses the Base Attack Complexity (AC). Modified attack requirements (MAT:X) Not defined: scoring uses the Base Attack Requirements (AT). Modified privileges required (MPR:X) Not defined: scoring uses the Base Privileges Required (PR). Modified user interaction (MUI:X) Not defined: scoring uses the Base User Interaction (UI). Modified vulnerable system confidentiality impact (MVC:X) Not defined: scoring uses the Base VC metric. Modified vulnerable system integrity impact (MVI:X) Not defined: scoring uses the Base VI metric. Modified vulnerable system availability impact (MVA:X) Not defined: scoring uses the Base VA metric. Modified subsequent system confidentiality impact (MSC:X) Not defined: scoring uses the Base SC metric. Modified subsequent system integrity impact (MSI:X) Not defined: scoring uses the Base SI metric. Modified subsequent system availability impact (MSA:X) Not defined: scoring uses the Base SA metric. Safety (supplemental) (S:X) Not evaluated. Automatable (supplemental) (AU:X) Not evaluated. Recovery (supplemental) (R:X) Not evaluated. Value density (supplemental) (V:X) Not evaluated. Vulnerability response effort (supplemental) (RE:X) Not evaluated. Provider urgency (supplemental) (U:X) Not evaluated.	—	—	[email protected]
8.2	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:L) Attackers could change some data, but it’s limited—not everything goes. Availability (A:N) Service keeps running; no real outage angle.	3.9	4.2	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

4.0

HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network.
Attack complexity (AC:L): Exploitation conditions are straightforward and stable.
Attack requirements (AT:N): No additional preconditions are required beyond normal reachability.
Privileges required (PR:N): No privileges are required.
User interaction (UI:N): No user interaction is required.
Vulnerable system confidentiality impact (VC:H): High confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:L): Limited integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:N): No availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N): No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N): No integrity impact on subsequent systems.
Subsequent system availability impact (SA:N): No availability impact on subsequent systems.
Exploit maturity (threat) (E:X): Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X): Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X): Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X): Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X): Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X): Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X): Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X): Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X): Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X): Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X): Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X): Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X): Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X): Not evaluated.
Automatable (supplemental) (AU:X): Not evaluated.
Recovery (supplemental) (R:X): Not evaluated.
Value density (supplemental) (V:X): Not evaluated.
Vulnerability response effort (supplemental) (RE:X): Not evaluated.
Provider urgency (supplemental) (U:X): Not evaluated.

—

[email protected]

8.2

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:L): Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N): Service keeps running; no real outage angle.

3.9

4.2

[email protected]

OS Trackers for CVE-2026-50168

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2026-50168 not yet assigned priority: Debian including 1 source packages (angular.js), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): undetermined 5.	https://security-tracker.debian.org/tracker/CVE-2026-50168
`ubuntu`	medium	CVE-2026-50168 medium priority: Ubuntu including 1 source packages (angular.js), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, resolute, upstream, xenial): needs-triage 8.	https://ubuntu.com/security/CVE-2026-50168

Affected software / configurations for CVE-2026-50168

Vendor	Product	Version	Raw CPE
angular	angular	>= 2.0.0, <= 18.2.14	cpe:2.3:a:angular:angular::::::node.js::*
angular	angular	>= 19.0.0, < 19.2.23	cpe:2.3:a:angular:angular::::::node.js::*
angular	angular	>= 20.0.0, < 20.3.22	cpe:2.3:a:angular:angular::::::node.js::*
angular	angular	>= 21.0.0, < 21.2.15	cpe:2.3:a:angular:angular::::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next0::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next1::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next10::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next11::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next12::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next2::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next3::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next4::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next5::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next6::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next7::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next8::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:next9::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:rc0::::node.js::*
angular	angular	22.0.0	cpe:2.3:a:angular:angular:22.0.0:rc1::::node.js::*

References for CVE-2026-50168

URL	Tags
https://github.com/angular/angular/pull/68928	Issue Tracking Patch
https://github.com/angular/angular/security/advisories/GHSA-xrxm-cp7j-8xf6	Vendor Advisory

URL

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

Exploit prediction scoring system (EPSS) score for CVE-2026-50168

Common vulnerability scoring system (CVSS) metrics for CVE-2026-50168

Weakness enumeration for CVE-2026-50168

GitHub Security Advisory for CVE-2026-50168

OS Trackers for CVE-2026-50168

Affected software / configurations for CVE-2026-50168

References for CVE-2026-50168