# CVE-2026-50170: Angular: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache > Attackers can leak private user data via cached SSR pages when Angular's HttpTransferCache fails to exclude credentialed requests. - **Severity:** High 8.2 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Jun 2026 - **Updated:** 23 Jun 2026 - **Also known as:** DEBIAN-CVE-2026-50170, GHSA-q6f4-qqrg-jv6x, UBUNTU-CVE-2026-50170 ## What is CVE-2026-50170? CVE-2026-50170 is a high-severity vulnerability in angular, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-524 (Use of Cache Containing Sensitive Information) ## Which versions are affected by CVE-2026-50170? 10 open source packages ship an affected version, including @angular/common. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@angular/common` | npm | All versions to 18.2.14 | None | | `@angular/common` | npm | All versions to 18.2.14 | None | | `@angular/common` | npm | From 19.0.0-next.0 | 19.2.23 | | `@angular/common` | npm | From 19.0.0-next.0 | 19.2.23 | | `@angular/common` | npm | From 20.0.0-next.0 | 20.3.22 | | `@angular/common` | npm | From 20.0.0-next.0 | 20.3.22 | | `@angular/common` | npm | From 21.0.0-next.0 | 21.2.15 | | `@angular/common` | npm | From 21.0.0-next.0 | 21.2.15 | | `@angular/common` | npm | From 22.0.0-next.0 | 22.0.0-rc.2 | | `@angular/common` | npm | From 22.0.0-next.0 | 22.0.0-rc.2 | Products: Angular Angular. ## How do I fix CVE-2026-50170? Upgrade @angular/common to a fixed version for your release line: 19.2.23, 20.3.22, 21.2.15 or 22.0.0-rc.2. ## Is CVE-2026-50170 being exploited? There is no known exploitation of CVE-2026-50170 in the wild and no public exploit code. ## Other vulnerabilities in angular - [CVE-2026-68945](https://insights.sbomify.com/CVE-2026-68945/): Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning (high 8.8) - [CVE-2026-46417](https://insights.sbomify.com/CVE-2026-46417/): Angular: SSRF via Hostname Hijacking in @angular/platform-server (high 8.8) - [CVE-2026-50168](https://insights.sbomify.com/CVE-2026-50168/): Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass (high 8.8) - [CVE-2026-54266](https://insights.sbomify.com/CVE-2026-54266/): Angular: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning (high 8.8) - [CVE-2026-41423](https://insights.sbomify.com/CVE-2026-41423/): Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-50170 and fix it if it is affected. What it is: CVE-2026-50170 is a high-severity vulnerability in angular, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-50170 in the wild and no public exploit code. Affected packages and fixed versions: - @angular/common (npm): affected all versions up to 18.2.14; no fix listed - @angular/common (npm): affected all versions up to 18.2.14; no fix listed - @angular/common (npm): affected from 19.0.0-next.0; fixed in 19.2.23 - @angular/common (npm): affected from 19.0.0-next.0; fixed in 19.2.23 - @angular/common (npm): affected from 20.0.0-next.0; fixed in 20.3.22 - @angular/common (npm): affected from 20.0.0-next.0; fixed in 20.3.22 - @angular/common (npm): affected from 21.0.0-next.0; fixed in 21.2.15 - @angular/common (npm): affected from 21.0.0-next.0; fixed in 21.2.15 - @angular/common (npm): affected from 22.0.0-next.0; fixed in 22.0.0-rc.2 - @angular/common (npm): affected from 22.0.0-next.0; fixed in 22.0.0-rc.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-50170/ (Markdown: https://insights.sbomify.com/CVE-2026-50170/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50170 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50170 - OSV: https://osv.dev/vulnerability/CVE-2026-50170 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-50170/ Summaries are generated and may contain mistakes; the official description above is the record.