CVE-2026-50169: Angular Service Worker redirect policy bypass in @angular/service-worker

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

A vulnerability in the Angular Service Worker library could allow unauthorized access to sensitive user data. The component, which helps web applications work offline and load faster, fails to respect security settings that should block automatic redirects to private pages. If a user visits a specially crafted link while logged into a site using this library, their private account information or session cookies could be exposed to parts of the application that should not have access to them.

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

Quick answers

Is CVE-2026-50169 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-50169 being exploited in the wild.
How severe is CVE-2026-50169?
Medium severity, with a CVSS score of 3.1, published 22 June 2026.
Which products and versions are affected?
Google Service Worker < 18.2.14, >= 19.0.0-next.0, < 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; @angular/service-worker (npm) SEMVER:introduced=22.0.0-next.0,fixed=22.0.0-rc.2.
Is there a fix for CVE-2026-50169?
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-50169 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-50169?
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 the internal helper function `AssetGroup.newRequestWithMetadata()` fails to preserve the `redirect` policy of a Request object during reconstruction. When the Service Worker intercepts a request configured with a strict policy (e.g., `redirect: 'error'`), it strips this configuration and reverts to the browser's default 'follow' strategy. An attacker can exploit this 'Confused Deputy' scenario if a public route matched by the Service Worker redirects to a sensitive, session-restricted same-origin endpoint. If a victim has an active session, the Service Worker will transparently follow the redirect and return protected data to the client-side code, bypassing developer-defined security boundaries. 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/service-worker < 19.2.23, >= 19.0.0-next.0; < 20.3.22, >= 20.0.0-next.0; < 21.2.15, >= 21.0.0-next.0; < 22.0.0-rc.2, >= 22.0.0-next.0; <= 18.2.14

Identifiers

  • CVE-2026-50169
  • GHSA-gv2q-mqqv-365m

Timeline

  • 2026-03-06: other: Initial pull request submitted to fix the issue
  • 2026-03-18: patched: Fix merged into Angular 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.