Answer in brief
CVE-2026-88059 records a Medium severity (CVSS 4.0) vulnerability in Angular: Information Leak via `HttpTransferCache` Bypass When Using `withRequestsMadeViaParent`. The current sources do not mark it as known exploited. The current feed maps angular/angular (generic), @angular/common (npm), @angular/common (npm), @angular/common (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps angular/angular (generic), @angular/common (npm), @angular/common (npm), @angular/common (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:angular:angular:*:*:*:*:*:node.js:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| angular/angulargeneric | <=19.2.25 || >=20.0.0 <20.3.28 || >=21.0.0 <21.2.20 || >=22.0.0 <22.1.1 | 20.3.28, 21.2.20, 22.1.1 |
| @angular/commonnpm | >=20.0.0,<20.3.28 | 20.3.28 |
| @angular/commonnpm | <=19.2.25 | Not reported |
| @angular/commonnpm | >=22.0.0 <22.1.1 | 22.1.1 |
| @angular/commonnpm | >=21.0.0 <21.2.20 | 21.2.20 |
| @angular/commonnpm | >=20.0.0 <20.3.28 | 20.3.28 |
| @angular/commonnpm | >=0 | Not reported |
| @angular/commonnpm | >=22.0.0,<22.1.1 | 22.1.1 |
| @angular/commonnpm | >=21.0.0,<21.2.20 | 21.2.20 |
Published upstream
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.