CVE-2026-88056 Angular: SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR
Attackers can exploit URL parsing discrepancies in Angular SSR to trigger SSRF and disclose sensitive server-side credentials.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-88056?
CVE-2026-88056 is a high-severity server-side request forgery vulnerability in angular, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-918
Which versions are affected by CVE-2026-88056?
8 open source packages ship an affected version, including @angular/platform-server. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
@angular/platform-server npm | All versions to 19.2.25 | None |
@angular/platform-server npm | All versions to 19.2.25 | None |
@angular/platform-server npm | From 20.0.0 | 20.3.30 |
@angular/platform-server npm | From 20.0.0 | 20.3.30 |
@angular/platform-server npm | From 21.0.0 | 21.2.22 |
@angular/platform-server npm | From 21.0.0 | 21.2.22 |
2 more packages
@angular/platform-server npm | From 22.0.0 | 22.1.4 |
@angular/platform-server npm | From 22.0.0 | 22.1.4 |
Products include Angular Angular.
How do I fix CVE-2026-88056?
Upgrade @angular/platform-server to a fixed version for your release line: 20.3.30, 21.2.22 or 22.1.4.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-88056 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88056 exists.
Other vulnerabilities in angular
- CVE-2026-68945 Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
- CVE-2026-46417 Angular: SSRF via Hostname Hijacking in @angular/platform-server
- CVE-2026-50168 Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass
- CVE-2026-54266 Angular: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning
- CVE-2026-41423 Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server
Sources
Also known as DEBIAN-CVE-2026-88056, GHSA-f6mr-pjwc-34m4, UBUNTU-CVE-2026-88056.