dbcve.org
AngularFramework / library

CVE-2026-50170

HIGH · 7.5 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to 19.2.23 / 20.3.22 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AngularFramework / library
Affected:<= 18.2.14>= 19.0.0, < 19.2.23>= 20.0.0, < 20.3.22>= 21.0.0, < 21.2.15= 22.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 19.2.23 / 20.3.22 / 21.2.15 or later
Fixed in 19.2.2320.3.2221.2.15
Vendor patch github.com →
Recommended fix High confidence

Upgrade to 19.2.23 (for 19.x users), 20.3.22 (for 20.x users), 21.2.15 (for 21.x users), or 22.0.0-rc.2 (for 22.x users) - prefer the latest stable in your major version line

  1. 1. Identify the current Angular version in your project by checking package.json
  2. 2. If using Angular 18.x or earlier: upgrade to Angular 19.2.23 or later (recommended: latest 19.x stable)
  3. 3. If using Angular 19.x: upgrade to Angular 19.2.23 or later (recommended: latest 19.x stable)
  4. 4. If using Angular 20.x: upgrade to Angular 20.3.22 or later (recommended: latest 20.x stable)
  5. 5. If using Angular 21.x: upgrade to Angular 21.2.15 or later (recommended: latest 21.x stable)
  6. 6. Run npm install or yarn install to update dependencies
  7. 7. Test the application, specifically SSR and hydration functionality, to ensure the fix works correctly
  8. 8. Verify that HttpTransferCache now properly handles requests with withCredentials=true or Cookie headers
Caveat Angular major version upgrades may include breaking changes; review the Angular update guide (update.angular.io) for any required migration steps between major versions

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50170 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50170 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data