What is CVE-2026-50170?

CVE-2026-50170 is a high-severity security vulnerability in @angular/common (npm), affecting versions >= 22.0.0-next.0, < 22.0.0-rc.2. It is fixed in 22.0.0-rc.2, 20.3.22, 19.2.23, 21.2.15.

How severe is CVE-2026-50170?

CVE-2026-50170 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of @angular/common are affected by CVE-2026-50170?

@angular/common (npm) versions >= 22.0.0-next.0, < 22.0.0-rc.2 is affected.

Is there a fix for CVE-2026-50170?

Yes. CVE-2026-50170 is fixed in 22.0.0-rc.2, 20.3.22, 19.2.23, 21.2.15. Upgrade to this version or later.

Is CVE-2026-50170 exploitable, and should I be worried?

Whether CVE-2026-50170 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-50170 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-50170?

Upgrade: @angular/common to 22.0.0-rc.2 or later, @angular/common to 20.3.22 or later, @angular/common to 19.2.23 or later, @angular/common to 21.2.15 or later.

CVE-2026-50170 in @angular/common

Q: How severe is CVE-2026-50170?

CVE-2026-50170 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of @angular/common are affected by CVE-2026-50170?

@angular/common (npm) versions >= 22.0.0-next.0, < 22.0.0-rc.2 is affected.

Q: Is there a fix for CVE-2026-50170?

Yes. CVE-2026-50170 is fixed in 22.0.0-rc.2, 20.3.22, 19.2.23, 21.2.15. Upgrade to this version or later.

Q: Is CVE-2026-50170 exploitable, and should I be worried?

Whether CVE-2026-50170 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-50170 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-50170?

Upgrade: @angular/common to 22.0.0-rc.2 or later, @angular/common to 20.3.22 or later, @angular/common to 19.2.23 or later, @angular/common to 21.2.15 or later.

Summary

@angular/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache

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.

Attack Preconditions

SSR and Hydration Enabled: The Angular application must be configured to use Server-Side Rendering and hydration (e.g., using provideClientHydration()).
Credentialed Requests during SSR: The application must perform HTTP requests that require user-specific authentication (using cookies or withCredentials: true) during the initial server-side render.
Shared Caching: The application's HTML responses must be cached by a shared caching layer (CDN, reverse proxy, or server-side cache) without proper cache-control headers to distinguish authenticated users.

Impact

Successful exploitation allows an unauthenticated attacker to obtain sensitive, user-specific information of other authenticated users. This occurs when:

The SSR-rendered HTML containing the cached private data is stored in a shared cache (e.g., CDN, reverse proxy).
Subsequent requests for the same page receive the cached HTML containing the first user's private data.

CVE-2026-50170 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (22.0.0-rc.2, 20.3.22, 19.2.23, 21.2.15); upgrading removes the vulnerable code path.

Affected versions

@angular/common (>= 22.0.0-next.0, < 22.0.0-rc.2) @angular/common (>= 20.0.0-next.0, < 20.3.22) @angular/common (>= 19.0.0-next.0, < 19.2.23) @angular/common (<= 18.2.14) @angular/common (>= 21.0.0-next.0, < 21.2.15)

Security releases

@angular/common → 22.0.0-rc.2 (npm) @angular/common → 20.3.22 (npm) @angular/common → 19.2.23 (npm) @angular/common → 21.2.15 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

22.0.0-rc.2
21.2.15
20.3.22
19.2.23

Frequently Asked Questions

What is CVE-2026-50170? CVE-2026-50170 is a high-severity security vulnerability in @angular/common (npm), affecting versions >= 22.0.0-next.0, < 22.0.0-rc.2. It is fixed in 22.0.0-rc.2, 20.3.22, 19.2.23, 21.2.15.
How severe is CVE-2026-50170? CVE-2026-50170 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of @angular/common are affected by CVE-2026-50170? @angular/common (npm) versions >= 22.0.0-next.0, < 22.0.0-rc.2 is affected.
Is there a fix for CVE-2026-50170? Yes. CVE-2026-50170 is fixed in 22.0.0-rc.2, 20.3.22, 19.2.23, 21.2.15. Upgrade to this version or later.
Is CVE-2026-50170 exploitable, and should I be worried? Whether CVE-2026-50170 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-50170 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-50170?
- Upgrade @angular/common to 22.0.0-rc.2 or later
- Upgrade @angular/common to 20.3.22 or later
- Upgrade @angular/common to 19.2.23 or later
- Upgrade @angular/common to 21.2.15 or later

Other vulnerabilities in @angular/common

CVE-IDSeverityPackage summary

CVE-2026-54268High@angular/common: @angular/common: Denial of Service (DoS) via OOM in Date Formatting (formatDate)CVE-2026-54266High@angular/common: @angular/common: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning CVE-2026-50171High@angular/common: @angular/common: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)CVE-2025-66035High@angular/common: Angular is Vulnerable to XSRF Token Leakage via Protocol-Relative URLs in Angular HTTP Client