CVE-2026-54266: @angular/common Weak 32-Bit Cache Key Hashing Vulnerability
HIGHCVE-2026-54266 is a HIGH (CVSS 6.1) weak 32-bit cache key hashing vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting @angular/common libraries in the npm ecosystem. The issue involves weak 32-bit cache key hashing in `httptransfercache` leading to cross-request data leakage and state poisoning. Remediation is available by upgrading affected packages to version 22.0.1, 21.2.17, 20.3.25.
CVE-2026-54266 at a Glance
Security Impact
CVSS: 6.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).
How to Fix CVE-2026-54266
To remediate this vulnerability, upgrade all affected @angular/common dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @angular/common@22.0.1
npm install @angular/common@21.2.17
npm install @angular/common@20.3.25
npm install @angular/common@Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @angular/common
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-54266, inspect your project dependencies using npm:
npm ls @angular/common
Analyze the terminal output to locate any version of @angular/common in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 22.0.1), your application is affected.
Note: The npm ls @angular/common command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In @angular/common, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-54266 Affected @angular/common Versions
4 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@angular/common
|
npm |
≥ 22.0.0-next.0
< 22.0.1
|
22.0.1
|
|
@angular/common
|
npm |
≥ 21.0.0-next.0
< 21.2.17
|
21.2.17
|
|
@angular/common
|
npm |
≥ 20.0.0-next.0
< 20.3.25
|
20.3.25
|
|
@angular/common
|
npm |
≤ 19.2.25
|
|
References
Frequently Asked Questions
What is CVE-2026-54266?
Which @angular/common versions are affected?
What version fixes CVE-2026-54266?
Is @angular/common affected?
What is the CVSS score of CVE-2026-54266?
What CWE is associated with CVE-2026-54266?
How can I check npm dependencies for CVE-2026-54266?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-39pv-4j6c-2g6v",
"modified" : "2026-07-15T22:03:56Z",
"published" : "2026-06-15T17:24:02Z",
"aliases" : [ "CVE-2026-54266" ],
"summary" : "@angular/common: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning",
"details" : "Angular's `HttpTransferCache` caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during client-side hydration. This avoids repeating the same HTTP requests on the client. The cached responses are stored in `TransferState` using a cache key generated by hashing request properties (method, response type, mapped URL, serialized body, and sorted query parameters).\n\nThe cache keys are generated using a weak 32-bit DJB2-like polynomial rolling hash. The 32-bit hash space is extremely small, allowing attackers to find hash collisions.\n\nAn attacker can easily find a query parameter string (e.g., `q=aaCAZMMM` for a search request) that produces the exact same 32-bit hash as a sensitive endpoint (e.g., `/api/user/profile`). When a victim visits a crafted link containing the colliding parameter, the SSR process executes both the search request and the profile request. Due to the hash collision, the search response overwrites the profile response in the `TransferState` cache.\n\n### Impact\n\nWhen the application attempts to retrieve the cached response for the sensitive endpoint (such as the user's profile), it receives the attacker-controlled response instead. This results in:\n\n* **State Poisoning**: The application runs with attacker-forged data, which can lead to bypassing client-side security controls or DOM-based Cross-Site Scripting (XSS) if the data is rendered unsafely. \n* **Information Leakage**: If the sensitive response is mistakenly associated with the attacker's search results and rendered on the page, the victim's sensitive data may be disclosed to the attacker.\n\n### Patched Versions\n* 22.0.1 \n* 21.2.17 \n* 20.3.25\n\n### Framework-Level Fix\n\nThe logic has been updated to use a cryptographically secure **SHA-256** hash algorithm for generating `TransferState` cache keys in `HttpTransferCache`. The cache keys are now 256-bit hexadecimal strings.\n\n### Workarounds\n\nIf you cannot upgrade immediately, configure your `HttpClient` requests to skip transfer caching for sensitive endpoints:\n\n```ts\nthis.http.get('/api/user/profile', {\n transferCache: false\n});\n```\n\nAlternatively, disable the HTTP transfer cache globally in your application bootstrap config:\n\n```ts\n\nimport { provideClientHydration, withNoHttpTransferCache } from '@angular/platform-browser';\n\nexport const appConfig = {\n providers: [\n provideClientHydration(\n withNoHttpTransferCache()\n )\n ]\n};\n\n```\n\n### Credits\nThis vulnerability was discovered and reported by [CodeMender from Google DeepMind](https://deepmind.google/blog/introducing-codemender-an-ai-agent-for-code-security/).",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N"
}, {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@angular/common"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "22.0.0-next.0"
}, {
"fixed" : "22.0.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@angular/common"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "21.0.0-next.0"
}, {
"fixed" : "21.2.17"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@angular/common"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "20.0.0-next.0"
}, {
"fixed" : "20.3.25"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@angular/common"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "19.2.25"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/angular/angular/security/advisories/GHSA-39pv-4j6c-2g6v"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-54266"
}, {
"type" : "WEB",
"url" : "https://github.com/angular/angular/pull/69153"
}, {
"type" : "WEB",
"url" : "https://github.com/angular/angular/commit/5f36274da3f961430ae72865159afa02a1dd9133"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/angular/angular"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-328", "CWE-345" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-15T17:24:02Z",
"nvd_published_at" : "2026-06-22T16:16:39Z"
}
}