NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-50170: @angular/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache

highCVSS 4.0 8.2 · 3.1 7.5GHSA-q6f4-qqrg-jv6x

A vulnerability was discovered in @angular/common when Server-Side Rendering (SSR) and hydration are enabled. The HttpTransferCache utility optimizes hydration by caching outgoing HTTP requests performed during SSR and transferring the cached state to the client-side application via TransferState. However, the caching mechanism fails to inspect the withCredentials flag or the Cookie header of outgoing requests.

Published Jun 15, 2026 · Updated Jul 15, 2026

Affected packages

@angular/common

Ecosystem
npm
Affected
>= 22.0.0-next.0, < 22.0.0-rc.2
Fixed in
22.0.0-rc.2
Check
npm ls @angular/common

@angular/common

Ecosystem
npm
Affected
>= 20.0.0-next.0, < 20.3.22
Fixed in
20.3.22
Check
npm ls @angular/common

@angular/common

Ecosystem
npm
Affected
>= 19.0.0-next.0, < 19.2.23
Fixed in
19.2.23
Check
npm ls @angular/common

@angular/common

Ecosystem
npm
Affected
<= 18.2.14
Fixed in
No patched version yet
Check
npm ls @angular/common

@angular/common

Ecosystem
npm
Affected
>= 21.0.0-next.0, < 21.2.15
Fixed in
21.2.15
Check
npm ls @angular/common

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

A vulnerability was discovered in @angular/common when Server-Side Rendering (SSR) and hydration are enabled. The HttpTransferCache utility optimizes hydration by caching outgoing HTTP requests performed during SSR and transferring the cached state to the client-side application via TransferState.

However, the caching mechanism fails to inspect the withCredentials flag or the Cookie header of outgoing requests. As a result, credentialed, user-specific responses may be cached by default in the shared TransferState payload. When these responses are serialized into the HTML, any caching layer (such as a CDN, reverse proxy, or shared server cache) that caches the SSR-rendered HTML page could inadvertently cache and leak one user's private data to other users, leading to a high-severity information disclosure vulnerability.

Impact

Successful exploitation allows an unauthenticated attacker to obtain sensitive, user-specific information of other authenticated users. This occurs when:

  • The SSR-rendered HTML containing the cached private data is stored in a shared cache (e.g., CDN, reverse proxy).
  • Subsequent requests for the same page receive the cached HTML containing the first user's private data.

Attack Preconditions

  • SSR and Hydration Enabled: The Angular application must be configured to use Server-Side Rendering and hydration (e.g., using provideClientHydration()).
  • Credentialed Requests during SSR: The application must perform HTTP requests that require user-specific authentication (using cookies or withCredentials: true) during the initial server-side render.
  • Shared Caching: The application's HTML responses must be cached by a shared caching layer (CDN, reverse proxy, or server-side cache) without proper cache-control headers to distinguish authenticated users.

Patches

  • 22.0.0-rc.2
  • 21.2.15
  • 20.3.22
  • 19.2.23

Credited to Yenya030, josephperrott, alan-agius4, AndrewKushnir, dgp1130.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries