# CVE-2026-54264: Angular: Sensitive Header Leakage on Cross-Origin Redirects in Angular Service Worker > Remote attackers can steal sensitive credentials like authorization tokens by triggering cross-origin redirects in the Angular Service Worker. - **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 22 Jun 2026 - **Updated:** 23 Jun 2026 - **Also known as:** DEBIAN-CVE-2026-54264, GHSA-qxh6-94w6-9r5p, UBUNTU-CVE-2026-54264 ## What is CVE-2026-54264? CVE-2026-54264 is a high-severity vulnerability in angular, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.1, 21.2.17, and 20.3.25, an information disclosure vulnerability exists in the @angular/service-worker package of the Angular framework. When the Service Worker fetches assets, it preserves metadata (such as headers) from the original request. However, on cross-origin redirects, the Service Worker fails to strip sensitive headers, violating the Fetch redirect algorithm. This allows a remote attacker to obtain sensitive credentials (e.g., Authorization tokens, Proxy-Authorization credentials, or session cookies) by triggering a cross-origin redirect to an untrusted external origin. This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25. Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2026-54264? 8 open source packages ship an affected version, including @angular/service-worker. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `@angular/service-worker` | npm | All versions to 19.2.25 | None | | `@angular/service-worker` | npm | All versions to 19.2.25 | None | | `@angular/service-worker` | npm | From 20.0.0-next.0 | 20.3.25 | | `@angular/service-worker` | npm | From 20.0.0-next.0 | 20.3.25 | | `@angular/service-worker` | npm | From 21.0.0-next.0 | 21.2.17 | | `@angular/service-worker` | npm | From 21.0.0-next.0 | 21.2.17 | | `@angular/service-worker` | npm | From 22.0.0-next.0 | 22.0.1 | | `@angular/service-worker` | npm | From 22.0.0-next.0 | 22.0.1 | Products: Angular Angular. ## How do I fix CVE-2026-54264? Upgrade @angular/service-worker to a fixed version for your release line: 20.3.25, 21.2.17 or 22.0.1. ## Is CVE-2026-54264 being exploited? There is no known exploitation of CVE-2026-54264 in the wild and no public exploit code. ## Other vulnerabilities in angular - [CVE-2026-68945](https://insights.sbomify.com/CVE-2026-68945/): Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning (high 8.8) - [CVE-2026-46417](https://insights.sbomify.com/CVE-2026-46417/): Angular: SSRF via Hostname Hijacking in @angular/platform-server (high 8.8) - [CVE-2026-50168](https://insights.sbomify.com/CVE-2026-50168/): Angular: URL Parser Differential in @angular/platform-server leading to SSRF Allowlist Bypass (high 8.8) - [CVE-2026-54266](https://insights.sbomify.com/CVE-2026-54266/): Angular: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning (high 8.8) - [CVE-2026-41423](https://insights.sbomify.com/CVE-2026-41423/): Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-54264 and fix it if it is affected. What it is: CVE-2026-54264 is a high-severity vulnerability in angular, published on 22 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-54264 in the wild and no public exploit code. Affected packages and fixed versions: - @angular/service-worker (npm): affected all versions up to 19.2.25; no fix listed - @angular/service-worker (npm): affected all versions up to 19.2.25; no fix listed - @angular/service-worker (npm): affected from 20.0.0-next.0; fixed in 20.3.25 - @angular/service-worker (npm): affected from 20.0.0-next.0; fixed in 20.3.25 - @angular/service-worker (npm): affected from 21.0.0-next.0; fixed in 21.2.17 - @angular/service-worker (npm): affected from 21.0.0-next.0; fixed in 21.2.17 - @angular/service-worker (npm): affected from 22.0.0-next.0; fixed in 22.0.1 - @angular/service-worker (npm): affected from 22.0.0-next.0; fixed in 22.0.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-54264/ (Markdown: https://insights.sbomify.com/CVE-2026-54264/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54264 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54264 - OSV: https://osv.dev/vulnerability/CVE-2026-54264 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-54264/ Summaries are generated and may contain mistakes; the official description above is the record.