CVE-2026-54266

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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, 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). The 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. An 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. This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
0.6%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 26, 2026

Advisory Details (3)

Auto-updated Jun 22, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning · Advisory · angular/angular · GitHub

https://github.com/angular/angular/security/advisories/GHSA-39pv-4j6c-2g6v
github_pr Patch Available

fix(common): use cryptographically secure SHA-256 for transfer cache key generation

Patch available: angular/angular v22.1.0-next.0 (PR #69153 merged 2026-06-05)

https://github.com/angular/angular/pull/69153
github_commit Patch Available

commit 5f36274da3f9 (angular/angular)

Patch available: angular/angular v22.1.0-next.0 (contains commit 5f36274da3f9)

https://github.com/angular/angular/commit/5f36274da3f961430ae72865159afa02a1dd9133

Vendor Advisories for CVE-2026-54266(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@angular/common

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 00:20 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 21:24 UTCEG score recompute
  7. 2026-07-04 18:59 UTCEG score recompute
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-03 14:17 UTCEG score recompute
  11. 2026-07-02 11:18 UTCEG score recompute
  12. 2026-07-01 15:07 UTCEPSS rescore
  13. 2026-07-01 09:08 UTCEG score recompute
  14. 2026-06-30 23:22 UTCEPSS rescore
  15. 2026-06-30 07:02 UTCEG score recompute
  16. 2026-06-29 04:51 UTCEG score recompute
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 01:56 UTCEG score recompute
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 23:52 UTCEG score recompute 2.70
  23. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 6.1 · severity → MEDIUM
  24. 2026-06-26 11:58 UTCEG score recompute
  25. 2026-06-25 20:16 UTCEG score recompute
Show 12 more
  1. 2026-06-25 13:49 UTCEPSS rescore
  2. 2026-06-25 08:20 UTCEG score recompute
  3. 2026-06-24 20:26 UTCEG score recompute
  4. 2026-06-24 14:05 UTCEPSS rescore
  5. 2026-06-24 06:43 UTCEG score recompute
  6. 2026-06-23 21:33 UTCEPSS rescore
  7. 2026-06-23 21:33 UTCEPSS rescore
  8. 2026-06-23 18:24 UTCEG score recompute
  9. 2026-06-23 06:23 UTCEG score recompute
  10. 2026-06-22 17:50 UTCEG score recompute 8.80
  11. 2026-06-22 17:45 UTCNVD updateCVSS v3 → 8.8 · CVSS v4 → 8.8
  12. 2026-06-15 17:46 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54266?
CVE-2026-54266 is a medium vulnerability published on June 15, 2026. 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, Angular's HttpTransferCache caches HTTP requests made during Server-Side Rendering (SSR) so that they can be reused during…
When was CVE-2026-54266 disclosed?
CVE-2026-54266 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54266 actively exploited?
CVE-2026-54266 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54266?
CVE-2026-54266 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-54266?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54266, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54266

Explore →

Is Your Infrastructure Affected by CVE-2026-54266?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.