Log in Start free

Vulnerability · Published Sep 10, 2026 · Assigned by GitHub_M

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

Medium 4.0

In plain English

A medium-severity information exposure in angular from angular. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 27% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)4.0Medium
Exploit odds (30 days)0.3%top 72.6% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12angular.jsno fix listedDEBIAN-CVE-2026-88059
Debian:13angular.jsno fix listedDEBIAN-CVE-2026-88059
Ubuntu:22.04:LTSangular.jsno fix listedUBUNTU-CVE-2026-88059
Ubuntu:24.04:LTSangular.jsno fix listedUBUNTU-CVE-2026-88059
Ubuntu:26.04:LTSangular.jsno fix listedUBUNTU-CVE-2026-88059
Ubuntu:26.10angular.jsno fix listedUBUNTU-CVE-2026-88059
npm@angular/commonno fix listedGHSA-p297-fm68-3q8c
npm@angular/common20.3.28GHSA-p297-fm68-3q8c
npm@angular/common22.1.1GHSA-p297-fm68-3q8c
npm@angular/common21.2.20GHSA-p297-fm68-3q8c

Affected products (as reported)

VendorProductVersions
angular angular <= 19.2.25>= 20.0.0, < 20.3.28>= 21.0.0, < 21.2.20>= 22.0.0, < 22.1.1

Weakness: CWE-200, CWE-524 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N

References