CVE-2026-50170
Angular: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache
Record summary
CVE-2026-50170 has a selected CVSS score of 8.2 (high).
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.
Exploitation context
CISA SSVC decision
CISA Coordinator · SSVC 2.0.3 · Evaluated Jun 23, 2026 · Source: CVE List
Affected products and versions
2| Product | Source | Version range | Status |
|---|---|---|---|
angularBrowse angular / angular | CVE List | >= 22.0.0-next.0, < 22.0.0-rc.2 | affected |
| >= 21.0.0-next.0, < 21.2.15 | affected | ||
| >= 20.0.0-next.0, < 20.3.22 | affected | ||
| >= 19.0.0-next.0, < 19.2.23 | affected | ||
| <= 18.2.14 | affected | ||
@angular/commonBrowse npm / @angular/common | GitHub Advisory | 22.0.0-next.0 to < 22.0.0-rc.2 · Fixed in 22.0.0-rc.2 | affected |
| 20.0.0-next.0 to < 20.3.22 · Fixed in 20.3.22 | affected | ||
| 19.0.0-next.0 to < 19.2.23 · Fixed in 19.2.23 | affected | ||
| Through 18.2.14 | affected | ||
| 21.0.0-next.0 to < 21.2.15 · Fixed in 21.2.15 | affected |