Answer in brief
CVE-2026-54264 records a High severity (CVSS 8.3) vulnerability in @angular/service-worker: Sensitive Header Leakage on Cross-Origin Redirects in Angular Service Worker. The current sources do not mark it as known exploited. The current feed maps @angular/service-worker (npm), @angular/service-worker (npm), @angular/service-worker (npm), @angular/service-worker (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps @angular/service-worker (npm), @angular/service-worker (npm), @angular/service-worker (npm), @angular/service-worker (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| @angular/service-workernpm | >=22.0.0-next.0,<22.0.1 | 22.0.1 |
| @angular/service-workernpm | >=21.0.0-next.0,<21.2.17 | 21.2.17 |
| @angular/service-workernpm | >=20.0.0-next.0,<20.3.25 | 20.3.25 |
| @angular/service-workernpm | <=19.2.25 | Not reported |
| @angular/service-workernpm | >=22.0.0-next.0<22.0.1 | Not reported |
| @angular/service-workernpm | >=21.0.0-next.0<21.2.17 | Not reported |
| @angular/service-workernpm | >=20.0.0-next.0<20.3.25 | Not reported |
Published upstream
Jun 10, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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. ### Impact If an application configured with the Angular Service Worker fetches assets with credential headers (such as `Authorization` header), and one of those requests is redirected to a different origin, the Service Worker will forward those headers to the new origin. This exposes critical credentials and session identifiers to unauthorized third-party servers. ### Attack Preconditions For this vulnerability to be exploitable: 1. **Vulnerable Configuration:** The application must utilize the `@angular/service-worker` package to fetch assets. 2. **Credentialed Requests:** The application must attach sensitive request headers (like `Authorization`, `Proxy-Authorization`, or rely on cookies) to asset-group requests. 3. **Redirect Flow:** These requests must encounter a cross-origin redirect to an attacker-controlled or untrusted domain. ### Patched Versions * 22.0.1 * 21.2.17 * 20.3.25 ### References * https://github.com/angular/angular/pull/69029 ### Credits This vulnerability was discovered and reported by [CodeMender from Google DeepMind](https://deepmind.google/blog/introducing-codemender-an-ai-agent-for-code-security/).
Quoted source text, attributed separately from HOL analysis.