Vulnerabilities in pkg:npm/@angular/service-worker

PACKAGE
Advisory Identifier: GHSA-95qp-cmmw-mgqv
Advisory Summary

CVE-2026-50184 is a MODERATE (CVSS 6.1) request credential & cache policy vulnerability (CWE-524: Use of Cache Containing Sensitive Information) affecting @angular/service-worker libraries in the npm ecosystem. The issue involves request credential & cache policy stripping. Remediation is available by upgrading affected packages to version 22.0.0-rc.2, 21.2.15, 20.3.22, 19.2.23.

3 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/@angular/service-worker

3 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/@angular/service-worker. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-95qp-cmmw-mgqv CVE-2026-50184 MODERATE @angular/service-worker: Request Credential & Cache Policy Stripping
GHSA-gv2q-mqqv-365m CVE-2026-50169 MODERATE Angular Service Worker Policy-Bypass & Credential-Stripping Vulnerabilities
GHSA-qxh6-94w6-9r5p CVE-2026-54264 HIGH @angular/service-worker: Sensitive Header Leakage on Cross-Origin Redirects in Angular Service Worker

CVE-2026-50184 at a Glance

CVE Identifier CVE-2026-50184
GHSA Identifier GHSA-95qp-cmmw-mgqv
Severity MODERATE
CVSS v3.1 Base Score 6.1
CWE Classification CWE-524: Use of Cache Containing Sensitive Information
Affected Product @angular/service-worker
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 6.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-50184

To remediate this vulnerability, upgrade all affected @angular/service-worker dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@angular/service-worker fixed: 22.0.0-rc.2
npm install @angular/service-worker@22.0.0-rc.2
@angular/service-worker fixed: 21.2.15
npm install @angular/service-worker@21.2.15
@angular/service-worker fixed: 20.3.22
npm install @angular/service-worker@20.3.22
@angular/service-worker fixed: 19.2.23
npm install @angular/service-worker@19.2.23
@angular/service-worker fixed: Latest secure release
npm install @angular/service-worker@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @angular/service-worker

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-50184, inspect your project dependencies using npm:

npm ls @angular/service-worker

Analyze the terminal output to locate any version of @angular/service-worker in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 22.0.0-rc.2), your application is affected.

Note: The npm ls @angular/service-worker command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-524: Use of Cache Containing Sensitive Information, where the code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. In @angular/service-worker, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

An issue in the `@angular/service-worker` package compromises the integrity of request-policy enforcement during request reconstruction. When the Angular Service Worker intercepts network requests for matched assets, it reconstructs a new `Request` object using an internal helper function. During this reconstruction process, the helper function strips explicit client-defined safety parameters: the credentials configuration (such as `credentials: 'omit'`) and the HTTP `cache` mode configuration (such as `cache: 'no-store'`). These are reverted back to standard browser-default parameters (`credentials: 'same-origin'` and default HTTP cache properties). This causes the browser to include active credentials (such as cookies or Authorization headers) on outbound requests where the client-side developer explicitly instructed they should be omitted, leading to potential session leaks. Additionally, it causes private or non-cacheable resources to be cached by the service worker's engine, making private page states accessible or persistent inside the client's local cache post-logout. ### Impact Web applications registering the `@angular/service-worker` package are vulnerable to credential exposure or post-logout cache persistence if client-side code relies on fetch calls with explicit safety attributes (such as `{ credentials: 'omit' }` or `{ cache: 'no-store' }`) targeting paths matched by service worker asset groups. By stripping these safety boundaries, the service worker exposes same-origin cookies and dynamic sensitive data to endpoints that should not receive them, or retains dynamic user sessions in cache storage where logout operations fail to fully evict user records. ### Attack Preconditions To successfully exploit this vulnerability, all of the following application states and parameters must concurrently exist: 1. **Active Angular Service Worker:** The target application uses `@angular/service-worker` and has an active registration of `ngsw-worker.js` inside the client's browser context. 2. **Asset Group Matching:** An `assetGroups` pattern in `ngsw-config.json` encompasses the target dynamic routing endpoint. 3. **Established User Session:** The victim user currently has an active authentication state, such as valid same-origin session cookies or auth headers stored by the browser. 4. **Client-Side Safe Fetch Call:** The application initiates an explicit fetch request to the route with safety parameters: `{ credentials: 'omit' }` or specific cache control parameters (e.g. `{ cache: 'no-store' }`). ### Mitigations & Workarounds If upgrading the `@angular/service-worker` package is not immediately feasible, developers should implement the following defensive measures: * **Strict Cookie Configuration:** Apply strict flags to session cookies (`SameSite=Strict; Secure; HttpOnly`) and ensure complete route isolation for credential-guarded secure resources. * **Exclude Secure Endpoints from SW Config:** Ensure that patterns targeting dynamic, secure endpoints are explicitly excluded from automatic asset groups or caching scopes in your `ngsw-config.json`. * **Post-Logout Cache Invalidation:** Programmatically purge the browser's Cache Storage API entries registered by the Angular Service Worker upon user logout: ```javascript if ('caches' in window) { caches.keys().then(names => { for (let name of names) { if (name.startsWith('ngsw:')) { caches.delete(name); } } }); } ``` ### Patches - 22.0.0-rc.2 - 21.2.15 - 20.3.22 - 19.2.23

CVE-2026-50184 Affected @angular/service-worker Versions

5 component(s)
Fixed Versions:
22.0.0-rc.221.2.1520.3.2219.2.23
Product / Package Ecosystem Affected Versions Fixed Version
@angular/service-worker
npm
≥ 22.0.0-next.0
< 22.0.0-rc.2
22.0.0-rc.2
@angular/service-worker
npm
≥ 21.0.0-next.0
< 21.2.15
21.2.15
@angular/service-worker
npm
≥ 20.0.0-next.0
< 20.3.22
20.3.22
@angular/service-worker
npm
≥ 19.0.0-next.0
< 19.2.23
19.2.23
@angular/service-worker
npm
≤ 18.2.14

References

Frequently Asked Questions

What is CVE-2026-50184?
CVE-2026-50184 is a security vulnerability in @angular/service-worker involving Request Credential & Cache Policy Stripping under CWE-524: Use of Cache Containing Sensitive Information.
Which @angular/service-worker versions are affected?
Affected versions include releases prior to 22.0.0-rc.2, 21.2.15, 20.3.22, 19.2.23 across affected packages: @angular/service-worker.
What version fixes CVE-2026-50184?
Upgrading to 22.0.0-rc.2, 21.2.15, 20.3.22, 19.2.23 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @angular/service-worker affected?
Yes, @angular/service-worker is affected in releases prior to 22.0.0-rc.2, 21.2.15, 20.3.22, 19.2.23, Latest secure release. Upgrade your dependency to 22.0.0-rc.2, 21.2.15, 20.3.22, 19.2.23, Latest secure release or later.
What is the CVSS score of CVE-2026-50184?
CVE-2026-50184 has a CVSS v3.1 base score of 6.1 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N.
What CWE is associated with CVE-2026-50184?
CVE-2026-50184 is classified under CWE-524: Use of Cache Containing Sensitive Information (The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.).
How can I check npm dependencies for CVE-2026-50184?
Run the dependency tree command: 'npm ls @angular/service-worker'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-95qp-cmmw-mgqv",
  "modified" : "2026-07-15T22:05:21Z",
  "published" : "2026-06-15T17:13:05Z",
  "aliases" : [ "CVE-2026-50184" ],
  "summary" : "@angular/service-worker: Request Credential & Cache Policy Stripping",
  "details" : "An issue in the `@angular/service-worker` package compromises the integrity of request-policy enforcement during request reconstruction. When the Angular Service Worker intercepts network requests for matched assets, it reconstructs a new `Request` object using an internal helper function.\n\nDuring this reconstruction process, the helper function strips explicit client-defined safety parameters: the credentials configuration (such as `credentials: 'omit'`) and the HTTP `cache` mode configuration (such as `cache: 'no-store'`). These are reverted back to standard browser-default parameters (`credentials: 'same-origin'` and default HTTP cache properties).\n\nThis causes the browser to include active credentials (such as cookies or Authorization headers) on outbound requests where the client-side developer explicitly instructed they should be omitted, leading to potential session leaks. Additionally, it causes private or non-cacheable resources to be cached by the service worker's engine, making private page states accessible or persistent inside the client's local cache post-logout.\n\n### Impact\nWeb applications registering the `@angular/service-worker` package are vulnerable to credential exposure or post-logout cache persistence if client-side code relies on fetch calls with explicit safety attributes (such as `{ credentials: 'omit' }` or `{ cache: 'no-store' }`) targeting paths matched by service worker asset groups. \n\nBy stripping these safety boundaries, the service worker exposes same-origin cookies and dynamic sensitive data to endpoints that should not receive them, or retains dynamic user sessions in cache storage where logout operations fail to fully evict user records.\n\n### Attack Preconditions\nTo successfully exploit this vulnerability, all of the following application states and parameters must concurrently exist:\n1. **Active Angular Service Worker:** The target application uses `@angular/service-worker` and has an active registration of `ngsw-worker.js` inside the client's browser context.\n2. **Asset Group Matching:** An `assetGroups` pattern in `ngsw-config.json` encompasses the target dynamic routing endpoint.\n3. **Established User Session:** The victim user currently has an active authentication state, such as valid same-origin session cookies or auth headers stored by the browser.\n4. **Client-Side Safe Fetch Call:** The application initiates an explicit fetch request to the route with safety parameters: `{ credentials: 'omit' }` or specific cache control parameters (e.g. `{ cache: 'no-store' }`).\n\n### Mitigations & Workarounds\nIf upgrading the `@angular/service-worker` package is not immediately feasible, developers should implement the following defensive measures:\n* **Strict Cookie Configuration:** Apply strict flags to session cookies (`SameSite=Strict; Secure; HttpOnly`) and ensure complete route isolation for credential-guarded secure resources.\n* **Exclude Secure Endpoints from SW Config:** Ensure that patterns targeting dynamic, secure endpoints are explicitly excluded from automatic asset groups or caching scopes in your `ngsw-config.json`.\n* **Post-Logout Cache Invalidation:** Programmatically purge the browser's Cache Storage API entries registered by the Angular Service Worker upon user logout:\n  ```javascript\n  if ('caches' in window) {\n    caches.keys().then(names => {\n      for (let name of names) {\n        if (name.startsWith('ngsw:')) {\n          caches.delete(name);\n        }\n      }\n    });\n  }\n  ```\n### Patches\n- 22.0.0-rc.2\n- 21.2.15\n- 20.3.22\n- 19.2.23",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/service-worker"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "22.0.0-next.0"
      }, {
        "fixed" : "22.0.0-rc.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/service-worker"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "21.0.0-next.0"
      }, {
        "fixed" : "21.2.15"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/service-worker"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "20.0.0-next.0"
      }, {
        "fixed" : "20.3.22"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/service-worker"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "19.0.0-next.0"
      }, {
        "fixed" : "19.2.23"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@angular/service-worker"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "18.2.14"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/security/advisories/GHSA-95qp-cmmw-mgqv"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-50184"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/angular/angular/pull/68904"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/angular/angular"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-524" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-15T17:13:05Z",
    "nvd_published_at" : "2026-06-22T18:16:42Z"
  }
}