# CVE-2026-88059: Angular: Information Leak via `HttpTransferCache` Bypass When Using `withRequestsMadeViaParent`

> Attackers can access sensitive authenticated data cached in SSR HTML due to improper HttpTransferCache handling in Angular applications.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-88059, GHSA-p297-fm68-3q8c, UBUNTU-CVE-2026-88059

## What is CVE-2026-88059?

CVE-2026-88059 is a medium-severity vulnerability in angular, published on 10 Sep 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 20.3.28, 21.2.20, and 22.1.1, Angular's @angular/common HttpTransferCache can cache an authenticated response when Server-Side Rendering (SSR) and hydration use a hierarchical HttpClient configured with withRequestsMadeViaParent. The child TransferCache evaluates an initially anonymous request before delegation, then a parent withInterceptors chain adds an Authorization header, cookie, or API token; although the parent cache skips the authenticated request, the child still stores the private response in TransferState serialized as JSON in the ng-state script. Exploitation requires provideClientHydration, child provideHttpClient delegation through withRequestsMadeViaParent, parent-level credential injection, and an SSR HTML response shared across users by a CDN, reverse proxy, or application cache. A later unauthenticated or unauthorized visitor can receive the cached HTML containing the earlier authenticated user's sensitive response data. Applications can mitigate by attaching credentials at the child, filtering sensitive endpoints with withHttpTransferCacheOptions, disabling transfer caching for sensitive routes, or marking personalized HTML private or no-store. This issue is fixed in versions 20.3.28, 21.2.20, and 22.1.1.

Weakness: CWE-524 (Use of Cache Containing Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-88059?

8 open source packages ship an affected version, including @angular/common. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@angular/common` | npm | All versions to 19.2.25 | None |
| `@angular/common` | npm | All versions to 19.2.25 | None |
| `@angular/common` | npm | From 20.0.0 | 20.3.28 |
| `@angular/common` | npm | From 20.0.0 | 20.3.28 |
| `@angular/common` | npm | From 21.0.0 | 21.2.20 |
| `@angular/common` | npm | From 21.0.0 | 21.2.20 |
| `@angular/common` | npm | From 22.0.0 | 22.1.1 |
| `@angular/common` | npm | From 22.0.0 | 22.1.1 |

Products: Angular Angular.

## How do I fix CVE-2026-88059?

Upgrade @angular/common to a fixed version for your release line: 20.3.28, 21.2.20 or 22.1.1.

## Is CVE-2026-88059 being exploited?

There is no known exploitation of CVE-2026-88059 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-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-88059 and fix it if it is affected.

What it is: CVE-2026-88059 is a medium-severity vulnerability in angular, published on 10 Sep 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-88059 in the wild and no public exploit code.

Affected packages and fixed versions:
- @angular/common (npm): affected all versions up to 19.2.25; no fix listed
- @angular/common (npm): affected all versions up to 19.2.25; no fix listed
- @angular/common (npm): affected from 20.0.0; fixed in 20.3.28
- @angular/common (npm): affected from 20.0.0; fixed in 20.3.28
- @angular/common (npm): affected from 21.0.0; fixed in 21.2.20
- @angular/common (npm): affected from 21.0.0; fixed in 21.2.20
- @angular/common (npm): affected from 22.0.0; fixed in 22.1.1
- @angular/common (npm): affected from 22.0.0; fixed in 22.1.1

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

## Sources

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

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