# CVE-2026-50168: Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass > Attackers can bypass SSRF allowlists in Angular server-side rendering by exploiting URL parser differences to force requests to arbitrary external endpoints. - **Severity:** High 8.8 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Jun 2026 - **Updated:** 22 Jun 2026 - **Also known as:** DEBIAN-CVE-2026-50168, GHSA-xrxm-cp7j-8xf6, UBUNTU-CVE-2026-50168 ## What is CVE-2026-50168? CVE-2026-50168 is a high-severity server-side request forgery vulnerability in angular, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-918 (Server-Side Request Forgery), CWE-346 (Origin Validation Error) ## Which versions are affected by CVE-2026-50168? 10 open source packages ship an affected version, including @angular/platform-server. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@angular/platform-server` | npm | All versions to 18.2.14 | None | | `@angular/platform-server` | npm | All versions to 18.2.14 | None | | `@angular/platform-server` | npm | From 19.0.0-next.0 | 19.2.23 | | `@angular/platform-server` | npm | From 19.0.0-next.0 | 19.2.23 | | `@angular/platform-server` | npm | From 20.0.0-next.0 | 20.3.22 | | `@angular/platform-server` | npm | From 20.0.0-next.0 | 20.3.22 | | `@angular/platform-server` | npm | From 21.0.0-next.0 | 21.2.15 | | `@angular/platform-server` | npm | From 21.0.0-next.0 | 21.2.15 | | `@angular/platform-server` | npm | From 22.0.0-next.0 | 22.0.0-rc.2 | | `@angular/platform-server` | npm | From 22.0.0-next.0 | 22.0.0-rc.2 | Products: Angular Angular. ## How do I fix CVE-2026-50168? Upgrade @angular/platform-server to a fixed version for your release line: 19.2.23, 20.3.22, 21.2.15 or 22.0.0-rc.2. ## Is CVE-2026-50168 being exploited? There is no known exploitation of CVE-2026-50168 in the wild and no public exploit code. ## Other vulnerabilities in angular - [CVE-2026-68945](https://insights.sbomify.com/CVE-2026-68945/): Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning (high 8.8) - [CVE-2026-46417](https://insights.sbomify.com/CVE-2026-46417/): Angular: SSRF via Hostname Hijacking in @angular/platform-server (high 8.8) - [CVE-2026-54266](https://insights.sbomify.com/CVE-2026-54266/): Angular: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning (high 8.8) - [CVE-2026-41423](https://insights.sbomify.com/CVE-2026-41423/): Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server (high 8.7) - [CVE-2026-88056](https://insights.sbomify.com/CVE-2026-88056/): Angular: SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR (high 8.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-50168 and fix it if it is affected. What it is: CVE-2026-50168 is a high-severity server-side request forgery vulnerability in angular, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-50168 in the wild and no public exploit code. Affected packages and fixed versions: - @angular/platform-server (npm): affected all versions up to 18.2.14; no fix listed - @angular/platform-server (npm): affected all versions up to 18.2.14; no fix listed - @angular/platform-server (npm): affected from 19.0.0-next.0; fixed in 19.2.23 - @angular/platform-server (npm): affected from 19.0.0-next.0; fixed in 19.2.23 - @angular/platform-server (npm): affected from 20.0.0-next.0; fixed in 20.3.22 - @angular/platform-server (npm): affected from 20.0.0-next.0; fixed in 20.3.22 - @angular/platform-server (npm): affected from 21.0.0-next.0; fixed in 21.2.15 - @angular/platform-server (npm): affected from 21.0.0-next.0; fixed in 21.2.15 - @angular/platform-server (npm): affected from 22.0.0-next.0; fixed in 22.0.0-rc.2 - @angular/platform-server (npm): affected from 22.0.0-next.0; fixed in 22.0.0-rc.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-50168/ (Markdown: https://insights.sbomify.com/CVE-2026-50168/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50168 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50168 - OSV: https://osv.dev/vulnerability/CVE-2026-50168 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-50168/ Summaries are generated and may contain mistakes; the official description above is the record.