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

- **Severity:** High 8.6 (`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`)
- **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:** Yes
- **Published:** 10 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-88056, GHSA-f6mr-pjwc-34m4, UBUNTU-CVE-2026-88056

## 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 (Server-Side Request Forgery)

## 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 | Ecosystem | 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 |
| `@angular/platform-server` | npm | From 22.0.0 | 22.1.4 |
| `@angular/platform-server` | npm | From 22.0.0 | 22.1.4 |

Products: 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.

## 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](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-50168](https://insights.sbomify.com/CVE-2026-50168/): Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass (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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-88056 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88056 exists.

Affected packages and fixed versions:
- @angular/platform-server (npm): affected all versions up to 19.2.25; no fix listed
- @angular/platform-server (npm): affected all versions up to 19.2.25; no fix listed
- @angular/platform-server (npm): affected from 20.0.0; fixed in 20.3.30
- @angular/platform-server (npm): affected from 20.0.0; fixed in 20.3.30
- @angular/platform-server (npm): affected from 21.0.0; fixed in 21.2.22
- @angular/platform-server (npm): affected from 21.0.0; fixed in 21.2.22
- @angular/platform-server (npm): affected from 22.0.0; fixed in 22.1.4
- @angular/platform-server (npm): affected from 22.0.0; fixed in 22.1.4

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-88056/ (Markdown: https://insights.sbomify.com/CVE-2026-88056/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-88056
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-88056
- OSV: https://osv.dev/vulnerability/CVE-2026-88056

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-88056/
Summaries are generated and may contain mistakes; the official description above is the record.