@angular/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache (CVE-2026-50170)
A high-severity information disclosure vulnerability exists in @angular/common versions up to 18.2.14 when Server-Side Rendering (SSR) and hydration are enabled. The HttpTransferCache utility caches HTTP requests during SSR but does not check the withCredentials flag or Cookie headers, causing credentialed, user-specific responses to be cached and potentially leaked via shared caches like CDNs or reverse proxies. This can expose private user data to other users if the SSR-rendered HTML is cached improperly.
AI Analysis
Technical Summary
The vulnerability in @angular/common's HttpTransferCache occurs because it caches outgoing HTTP requests during SSR without inspecting if requests are credentialed (withCredentials flag or Cookie header). When SSR and hydration are enabled, this cached state is serialized into the HTML and transferred to the client. If the SSR HTML is cached by a shared caching layer without proper cache-control headers, it can leak sensitive user-specific data to other users. Exploitation requires SSR with hydration enabled, credentialed HTTP requests during SSR, and shared caching of the SSR HTML. Fixed versions include 19.2.23, 20.3.22, 21.2.15, and 22.0.0-rc.2.
Potential Impact
An unauthenticated attacker can obtain sensitive, user-specific information from other authenticated users if the SSR-rendered HTML containing cached private data is stored in a shared cache and subsequently served to other users. This leads to a high-severity information disclosure vulnerability affecting user privacy.
Mitigation Recommendations
Fixes are available in @angular/common versions 19.2.23, 20.3.22, 21.2.15, and 22.0.0-rc.2. Users should upgrade to one of these patched versions to remediate the vulnerability. Until patched, ensure that shared caching layers (CDNs, reverse proxies) do not cache SSR-rendered HTML containing credentialed requests by configuring appropriate cache-control headers to prevent leakage.
@angular/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache (CVE-2026-50170)
Description
A high-severity information disclosure vulnerability exists in @angular/common versions up to 18.2.14 when Server-Side Rendering (SSR) and hydration are enabled. The HttpTransferCache utility caches HTTP requests during SSR but does not check the withCredentials flag or Cookie headers, causing credentialed, user-specific responses to be cached and potentially leaked via shared caches like CDNs or reverse proxies. This can expose private user data to other users if the SSR-rendered HTML is cached improperly.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in @angular/common's HttpTransferCache occurs because it caches outgoing HTTP requests during SSR without inspecting if requests are credentialed (withCredentials flag or Cookie header). When SSR and hydration are enabled, this cached state is serialized into the HTML and transferred to the client. If the SSR HTML is cached by a shared caching layer without proper cache-control headers, it can leak sensitive user-specific data to other users. Exploitation requires SSR with hydration enabled, credentialed HTTP requests during SSR, and shared caching of the SSR HTML. Fixed versions include 19.2.23, 20.3.22, 21.2.15, and 22.0.0-rc.2.
Potential Impact
An unauthenticated attacker can obtain sensitive, user-specific information from other authenticated users if the SSR-rendered HTML containing cached private data is stored in a shared cache and subsequently served to other users. This leads to a high-severity information disclosure vulnerability affecting user privacy.
Mitigation Recommendations
Fixes are available in @angular/common versions 19.2.23, 20.3.22, 21.2.15, and 22.0.0-rc.2. Users should upgrade to one of these patched versions to remediate the vulnerability. Until patched, ensure that shared caching layers (CDNs, reverse proxies) do not cache SSR-rendered HTML containing credentialed requests by configuring appropriate cache-control headers to prevent leakage.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-q6f4-qqrg-jv6x
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-50170"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a58b41068715ace43d67d58
Added to database: 07/16/2026, 10:36:00 UTC
Last enriched: 07/16/2026, 10:52:43 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.