CVE-2026-50184: Angular Service Worker credential and cache policy stripping

CVE-2026-50184 · Severity: medium · CVSS 3.1 · Published 2026-06-22

A vulnerability in the Angular Service Worker library can cause web applications to unintentionally send sensitive user credentials, such as login cookies, to servers even when developers have explicitly instructed the application to omit them. Additionally, private data that should never be stored may be saved in the browser's local cache, potentially allowing sensitive information to remain accessible on a device even after a user has logged out. This flaw undermines privacy controls intended to protect user sessions and sensitive data in web-based mobile and desktop applications.

Technologies: @angular/service-worker (npm). Vendors: Google, npm.

Quick answers

Is CVE-2026-50184 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-50184 being exploited in the wild.
How severe is CVE-2026-50184?
Medium severity, with a CVSS score of 3.1, published 22 June 2026.
Which products and versions are affected?
Google Service Worker >= 22.0.0-next.0, < 22.0.0-rc.2; >= 21.0.0-next.0, < 21.2.15; >= 20.0.0-next.0, < 20.3.22; >= 19.0.0-next.0, < 19.2.23; <= 18.2.14; @angular/service-worker (npm) SEMVER:introduced=22.0.0-next.0,fixed=22.0.0-rc.2.
Is there a fix for CVE-2026-50184?
Yes. @angular/service-worker (npm): upgrade to 22.0.0-rc.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-50184 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-50184?
Check whether you run Google Service Worker or @angular/service-worker (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • @angular/service-worker (npm): upgrade to 22.0.0-rc.2 or later
    npm install @angular/service-worker@22.0.0-rc.2

Technical details

A vulnerability exists in the @angular/service-worker package where an internal helper function used during request reconstruction strips explicit safety parameters from Fetch API Request objects. Specifically, when the service worker intercepts requests for matched assets, it reverts 'credentials: omit' to 'same-origin' and resets 'cache: no-store' to default browser behaviors. This results in the browser including active credentials (cookies or Authorization headers) on outbound requests that were intended to be anonymous, and causes non-cacheable resources to be stored in the service worker's engine. An attacker could potentially access private page states persistent in the local cache post-logout or intercept leaked session tokens. The issue is fixed in versions 19.2.23, 20.3.22, 21.2.15, and 22.0.0-rc.2.

Affected products

  • angular angular < 19.2.23, >= 20.0.0-next.0 < 20.3.22, >= 21.0.0-next.0 < 21.2.15, >= 22.0.0-next.0 < 22.0.0-rc.2

Identifiers

  • CVE-2026-50184
  • GHSA-95qp-cmmw-mgqv

Timeline

  • 2026-05-24: other: Fix pull request submitted
  • 2026-05-27: patched: Fix merged into main branch
  • 2026-05-28: advisory: GitHub Security Advisory published
  • 2026-06-22: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.