CVE 5.7 MEDIUM

Angular Service Worker Policy-Bypass & Credential-Stripping Vulnerabilities_CVE-2026-50169

5.7 / 10
MEDIUM
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

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.15 20.3.22, and 19.2.23, 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. This vulnerability is fixed in 22.0.0-rc.2, 21.2.15, 20.3.22, and 19.2.23.

Basic Information

ID CVE-2026-50169
Source GitHub_M
Published Jun 22, 2026 at 15:41
Modified Jun 22, 2026 at 15:46

Affected Product

Vendor angular
Product angular
Version >= 22.0.0-next.0, < 22.0.0-rc.2
Affected Versions angular angular >= 22.0.0-next.0, < 22.0.0-rc.2
angular angular >= 21.0.0-next.0, < 21.2.15
angular angular >= 20.0.0-next.0, < 20.3.22
angular angular >= 19.0.0-next.0, < 19.2.23
angular angular <= 18.2.14

CWE Classification

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.