CVE-2026-54266

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 6.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-15. NVD baseline CVSS 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-38269 (ENISA EUVD) · GHSA-39pv-4j6c-2g6v (GitHub Security Advisories)Source: ENISA EUVD

6.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1MEDIUMmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 15, 2026

Last Modified

July 9, 2026

Advisory Details (3)

Auto-updated Jun 22, 2026
Patch available. Sources: github_commit, github_pr, github.
GitHub advisoryMentions a patch (unverified)

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 pull request 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.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@angular/common @ 22.0.1 (fixes >= 22.0.0-next.0, < 22.0.1)—ghsa
npm@angular/common @ 21.2.17 (fixes >= 21.0.0-next.0, < 21.2.17)—ghsa
npm@angular/common @ 20.3.25 (fixes >= 20.0.0-next.0, < 20.3.25)—ghsa
npm@angular/common—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.2-2, 1.8.3-1, 1.8.3-2, 1.8.3-3
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-1, 1.8.3-1+deb12u1, 1.8.3-1+deb12u1~deb11u1, 1.8.3-2, 1.8.3-3
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-3
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
angular.js1.8.3-3
  • every version on: no fix on record
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@angular/common—
  • 22.0.0-next.0 up to 22.0.1: fixed in 22.0.1
  • 21.0.0-next.0 up to 21.2.17: fixed in 21.2.17
  • 20.0.0-next.0 up to 20.3.25: fixed in 20.3.25
  • every version through 19.2.25: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 150 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 50 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-11-01 07:44 UTCGHSA enrichmentGHSA-39pv-4j6c-2g6v · GitHub severity HIGH · GitHub CVSS 6.1
  3. 2026-11-01 07:44 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-30 11:25 UTCOSV refresh
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-25 14:19 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-22 21:22 UTCEG score recompute
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-18 03:31 UTCEG score recompute
  21. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 75 more
  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-12 15:56 UTCEG score recompute
  3. 2026-10-11 19:39 UTCEG score recompute
  4. 2026-10-11 16:55 UTCEG score recompute
  5. 2026-10-11 14:18 UTCEG score recompute
  6. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-03 07:39 UTCOSV refresh
  15. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  28. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-09-14 03:46 UTCEG score recompute
  30. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  33. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  34. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  35. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  36. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-08-30 22:59 UTCEG score recompute
  40. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  43. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  45. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-08-24 23:34 UTCEG score recompute
  47. 2026-08-23 09:48 UTCEG score recompute
  48. 2026-08-23 00:19 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  49. 2026-08-21 23:49 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  50. 2026-08-21 18:57 UTCEG score recompute
  51. 2026-08-20 22:55 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  52. 2026-08-20 16:21 UTCEG score recompute
  53. 2026-08-19 17:04 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  54. 2026-08-19 13:15 UTCEG score recompute
  55. 2026-08-18 13:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  56. 2026-08-17 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  57. 2026-08-16 16:21 UTCEG score recompute
  58. 2026-08-16 02:14 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  59. 2026-08-14 12:12 UTCEG score recompute
  60. 2026-08-13 22:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  61. 2026-08-11 06:01 UTCEG score recompute
  62. 2026-08-11 00:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  63. 2026-08-09 01:54 UTCEG score recompute
  64. 2026-08-08 16:37 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  65. 2026-08-07 23:50 UTCEG score recompute
  66. 2026-08-06 21:46 UTCEG score recompute
  67. 2026-08-06 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  68. 2026-08-05 19:42 UTCEG score recompute
  69. 2026-08-05 19:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  70. 2026-08-04 16:51 UTCEG score recompute
  71. 2026-08-04 15:10 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  72. 2026-08-03 14:44 UTCEG score recompute
  73. 2026-08-03 10:36 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  74. 2026-08-02 12:21 UTCEG score recompute
  75. 2026-08-02 02:27 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile

Frequently asked(5)

What is CVE-2026-54266?
CVE-2026-54266 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-54266 published?
The CVE record for CVE-2026-54266 was published on June 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 9, 2026; the record at its source may have been updated since.
Is CVE-2026-54266 actively exploited?
CVE-2026-54266 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
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?
A fix for CVE-2026-54266 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54266 are linked in the Vendor Advisories panel on this page.

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.