CVE-2026-88059

Angular: Information Leak via `HttpTransferCache` Bypass When Using `withRequestsMadeViaParent`

MEDIUM
5.8
CVSS Score
Published: September 10, 2026 at 07:00 PM UTC
Updated: September 29, 2026 at 09:09 PM UTC
1 product affected across 1 vendor@angular

Using angular by angular?

Get instant alerts when new vulnerabilities affect angular - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.8
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≤ 19.2.25v < 20.3.28v < 21.2.20v < 22.1.119.0.0 ≤ v ≤ 19.2.2520.0.0 ≤ v < 20.3.2821.0.0 ≤ v < 21.2.2022.0.0 ≤ v < 22.1.1
Affected range stops below 20.3.28, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.1.1, so it looks safe — our inference, not a vendor statement

References (9)

x_refsource_CONFIRMExploitMitigationVendor Advisory
Source: cverecord
https://github.com/angular/angular/security/advisories/GHSA-p297-fm68-3q8c
x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/angular/angular/issues/69777
x_refsource_MISCIssue TrackingPatch
Source: cverecord
https://github.com/angular/angular/pull/69778
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/angular/angular/releases/tag/v20.3.28
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/angular/angular/releases/tag/v21.2.20

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-200CWE-524

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card