Use of Cache Containing Sensitive Information Affecting @angular/service-worker package, versions <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
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-ANGULARSERVICEWORKER-17359151
- published17 Jun 2026
- disclosed15 Jun 2026
- creditUnknown
Introduced: 15 Jun 2026
CVE-2026-50184 (opens in a new tab)How to fix?
Upgrade @angular/service-worker to version 19.2.23, 20.3.22, 21.2.15, 22.0.0-rc.2 or higher.
Overview
@angular/service-worker is an Angular - service worker tooling!
Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information in the request reconstruction. An attacker can access sensitive session data or cached private resources by exploiting the stripping of explicit client-defined safety parameters, causing credentials to be sent when they should be omitted or private data to persist in cache.
Note: This is only exploitable if the application uses an active Angular Service Worker, the asset group pattern matches the targeted endpoint, the user has an active authenticated session, and the client initiates a fetch request with explicit safety parameters.
Workaround
This vulnerability can be mitigated by applying strict flags to session cookies, excluding secure endpoints from service worker asset groups, and programmatically purging the browser's Cache Storage API entries registered by the Angular Service Worker upon user logout.