CVE 5.7 MEDIUM

Angular: Request Credential & Cache Policy Stripping in Angular Service Worker_CVE-2026-50184

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 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. 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-50184
Source GitHub_M
Published Jun 22, 2026 at 15:42
Modified Jun 22, 2026 at 15:50

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.