Skip to content
VulniPulse
Advisory severityMedium6.1Red Hat Linux

Medium [CVE-2026-50184] @angular/service-worker: @angular/service-worker: Security flaw leads to session leaks and cached private data

This medium-severity Red Hat Linux advisory covers CVE-2026-50184.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-50184 Source published Source updated

VulniPulse record published Record updated

CVE-2026-50184
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

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.

Is CVE-2026-50184 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-50184 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-50184?

Upgrade to a fixed release named by Red Hat:

  • 22.0.0
  • 21.2.15
  • 20.3.22
  • 19.2.23

Confirm against the vendor advisory before you patch.

Affected versions
  • < 22.0.0-rc
  • < 21.2.15
  • < 20.3.22
  • < 19.2.23

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Fixed versions
  • 22.0.0
  • 21.2.15
  • 20.3.22
  • 19.2.23

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.