All vulnerabilities

Servers and applications

CVE-2026-50169

Request Redirect Policy Bypass in Angular Service Worker

Severity
Medium 5.7
Published
28 May 2026
Last changed
3 Jun 2026
Added to UpHeron
3 Nov 2026
Exploit chance
0.2% in the next 30 daysHigher than 13% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Information exposure (CWE-200)CWE-441
Attack
Needs local access · Only under certain conditions · No login needed · Needs someone to view a page or file
Attacker can
Read data
CVSS vector
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
Also known as
GHSA-gv2q-mqqv-365m
Sources
Project advisories (GitHub)

Description

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 the strict, client-defined request redirect policy configuration (such as redirect: 'error'), falling back to the browser's default 'follow' strategy.

If the target web application makes client-side requests with a strict policy (e.g., expecting a network error instead of automatically following redirects), the service worker will bypass this instruction and automatically follow HTTP 3xx redirects to other destinations. This acts as an unintended proxy/intermediary ("Confused Deputy") and can result in cookie/credential exposure or same-origin session-restricted data leakage if public dynamic routes redirect to sensitive routes.

From angular/angular's security advisory. Shortened; the full text is there.

Workarounds

If upgrading the @angular/service-worker package is not immediately feasible, developers should implement the following defensive measures:

  • Avoid Public-to-Private Dynamic Redirection: Refactor the server architecture so that public paths matched by service worker asset groups never issue HTTP 3xx redirects to authenticated same-origin secure endpoints.
  • Strict Cookie Configuration: Apply strict flags to session cookies (SameSite=Strict; Secure; HttpOnly) and consider explicit route isolations (such as subdomains) for credential-guarded private resources.
Workarounds as given by angular/angular's security advisory.

Affected software

SoftwareAffected versions
AngularServers and applications · github:angular/angular
  • Every version up to 18.2.14

About Angular

web application framework

From Wikidata, CC0 1.0.
Developers who used it in the past year
18.2%Stack Overflow Developer Survey 2025, 2025
Weekly downloads (npm)
8,195,583npm, 15 Nov 2026
GitHub stars
101,504GitHub, 15 Nov 2026
Forks
28,216GitHub, 15 Nov 2026
Latest release
v22.2.6GitHub, 15 Nov 2026
Released
12 Nov 2026GitHub
Developer
GoogleWikidata
License
MIT LicenseWikidata
Written in
TypeScriptWikidata
First released
15 Sept 2016Wikidata
First published on GitHub
18 Sept 2014GitHub

Release lines

ReleaseLatestSecurity fixes
2222.2.6Until 30 Jun 2028
2121.2.26Until 30 Jun 2027
2020.3.35Until 28 Nov 2026
1919.2.25Ended 19 May 2026
1818.2.14Ended 21 Nov 2025
1717.3.12Ended 15 May 2025

From endoflife.date.

References