{"answers":{"affected":"10 open source packages ship an affected version, including @angular/common. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-50170 in the wild and no public exploit code.","fix":"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.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-50170 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-50170 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @angular/common (npm): affected all versions up to 18.2.14; no fix listed\n- @angular/common (npm): affected all versions up to 18.2.14; no fix listed\n- @angular/common (npm): affected from 19.0.0-next.0; fixed in 19.2.23\n- @angular/common (npm): affected from 19.0.0-next.0; fixed in 19.2.23\n- @angular/common (npm): affected from 20.0.0-next.0; fixed in 20.3.22\n- @angular/common (npm): affected from 20.0.0-next.0; fixed in 20.3.22\n- @angular/common (npm): affected from 21.0.0-next.0; fixed in 21.2.15\n- @angular/common (npm): affected from 21.0.0-next.0; fixed in 21.2.15\n- @angular/common (npm): affected from 22.0.0-next.0; fixed in 22.0.0-rc.2\n- @angular/common (npm): affected from 22.0.0-next.0; fixed in 22.0.0-rc.2\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-50170/ (Markdown: https://insights.sbomify.com/CVE-2026-50170/index.md)","id":"CVE-2026-50170","markdown":"https://insights.sbomify.com/CVE-2026-50170/index.md","name":"CVE-2026-50170","record":{"aliases":["DEBIAN-CVE-2026-50170","GHSA-q6f4-qqrg-jv6x","UBUNTU-CVE-2026-50170"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Angular web framework","requires_auth":"none","summary":"Attackers can leak private user data via cached SSR pages when Angular's HttpTransferCache fails to exclude credentialed requests.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"angular","vendor":"angular"}],"cvss":{"score":8.2,"severity":"high","source":"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","version":"4.0"},"cwes":[{"id":"CWE-524","name":"Use of Cache Containing Sensitive Information"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Angular: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache","id":"CVE-2026-50170","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":10,"n_references":2,"next":{"headline":"Angular: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)","id":"CVE-2026-50171"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["18.2.14"],"package":"@angular/common","purl":null,"source":"GHSA-q6f4-qqrg-jv6x"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["18.2.14"],"package":"@angular/common","purl":"pkg:npm/%40angular/common","source":"GHSA-q6f4-qqrg-jv6x"},{"ecosystem":"npm","fixed":["19.2.23"],"introduced":["19.0.0-next.0"],"last_affected":[],"package":"@angular/common","purl":null,"source":"GHSA-q6f4-qqrg-jv6x"},{"ecosystem":"npm","fixed":["19.2.23"],"introduced":["19.0.0-next.0"],"last_affected":[],"package":"@angular/common","purl":"pkg:npm/%40angular/common","source":"GHSA-q6f4-qqrg-jv6x"},{"ecosystem":"npm","fixed":["20.3.22"],"introduced":["20.0.0-next.0"],"last_affected":[],"package":"@angular/common","purl":null,"source":"GHSA-q6f4-qqrg-jv6x"},{"ecosystem":"npm","fixed":["20.3.22"],"introduced":["20.0.0-next.0"],"last_affected":[],"package":"@angular/common","purl":"pkg:npm/%40angular/common","source":"GHSA-q6f4-qqrg-jv6x"},{"ecosystem":"npm","fixed":["21.2.15"],"introduced":["21.0.0-next.0"],"last_affected":[],"package":"@angular/common","purl":null,"source":"GHSA-q6f4-qqrg-jv6x"},{"ecosystem":"npm","fixed":["21.2.15"],"introduced":["21.0.0-next.0"],"last_affected":[],"package":"@angular/common","purl":"pkg:npm/%40angular/common","source":"GHSA-q6f4-qqrg-jv6x"},{"ecosystem":"npm","fixed":["22.0.0-rc.2"],"introduced":["22.0.0-next.0"],"last_affected":[],"package":"@angular/common","purl":null,"source":"GHSA-q6f4-qqrg-jv6x"},{"ecosystem":"npm","fixed":["22.0.0-rc.2"],"introduced":["22.0.0-next.0"],"last_affected":[],"package":"@angular/common","purl":"pkg:npm/%40angular/common","source":"GHSA-q6f4-qqrg-jv6x"}],"prev":{"headline":"Angular Service Worker Policy-Bypass \u0026 Credential-Stripping Vulnerabilities","id":"CVE-2026-50169"},"products":["angular"],"published":"2026-06-22","related":[{"cvss_score":8.8,"headline":"Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning","id":"CVE-2026-68945","kev_date_added":null,"published":"2026-08-03"},{"cvss_score":8.8,"headline":"Angular: SSRF via Hostname Hijacking in @angular/platform-server","id":"CVE-2026-46417","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":8.8,"headline":"Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass","id":"CVE-2026-50168","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":8.8,"headline":"Angular: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning","id":"CVE-2026-54266","kev_date_added":null,"published":"2026-06-22"},{"cvss_score":8.7,"headline":"Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server","id":"CVE-2026-41423","kev_date_added":null,"published":"2026-05-08"},{"cvss_score":8.6,"headline":"Angular: SSRF and Cross-Origin Credential Disclosure via URL Resolution Discrepancy in SSR","id":"CVE-2026-88056","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":8.6,"headline":"Angular: SSR XSS via Unescaped Processing Instruction (\u003c?...?\u003e) Nodes in Fallback Raw-Content Elements","id":"CVE-2026-88058","kev_date_added":null,"published":"2026-09-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-23","vendors":["angular"]},"summary":"Attackers can leak private user data via cached SSR pages when Angular's HttpTransferCache fails to exclude credentialed requests.","url":"https://insights.sbomify.com/CVE-2026-50170/"}