CVE-2026-54290

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% 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, secondary
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

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

Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.25, with credentials: true and no explicit origin (the default wildcard), the CORS Middleware reflects the request's Origin and sends Access-Control-Allow-Credentials: true. Any site can then make credentialed cross-origin requests and read the responses, exposing cookie-authenticated endpoints to arbitrary origins. This vulnerability is fixed in 4.12.25.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
16.0%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 22, 2026

Advisory Details (1)

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

CORS Middleware reflects any Origin with credentials when `origin` defaults to the wildcard · Advisory · honojs/hono · GitHub

https://github.com/honojs/hono/security/advisories/GHSA-88fw-hqm2-52qc

Vendor Advisories for CVE-2026-54290(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
hono—4.12.25—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 64× 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-06 23:15 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 06:49 UTCEG score recompute
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 19:42 UTCEG score recompute
  8. 2026-07-05 08:44 UTCEG score recompute
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 20:19 UTCEG score recompute
  12. 2026-07-04 09:21 UTCEG score recompute
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 19:23 UTCEG score recompute
  16. 2026-07-03 08:27 UTCEG score recompute
  17. 2026-07-02 21:25 UTCEG score recompute
  18. 2026-07-02 10:28 UTCEG score recompute
  19. 2026-07-01 23:32 UTCEG score recompute
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 12:35 UTCEG score recompute
  22. 2026-07-01 01:39 UTCEG score recompute
  23. 2026-06-30 23:22 UTCEPSS rescore
  24. 2026-06-30 14:42 UTCEG score recompute
  25. 2026-06-30 03:43 UTCEG score recompute
Show 39 more
  1. 2026-06-29 16:40 UTCEG score recompute
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-29 05:44 UTCEG score recompute
  5. 2026-06-28 18:40 UTCEG score recompute
  6. 2026-06-28 14:07 UTCEPSS rescore
  7. 2026-06-28 07:43 UTCEG score recompute
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-28 04:56 UTCEPSS rescore
  10. 2026-06-27 20:47 UTCEG score recompute
  11. 2026-06-27 09:49 UTCEG score recompute
  12. 2026-06-27 03:08 UTCEPSS rescore
  13. 2026-06-26 22:52 UTCEG score recompute
  14. 2026-06-26 11:51 UTCEG score recompute
  15. 2026-06-25 19:25 UTCEG score recompute
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-25 08:28 UTCEG score recompute
  18. 2026-06-24 21:32 UTCEG score recompute
  19. 2026-06-24 14:05 UTCEPSS rescore
  20. 2026-06-24 10:35 UTCEG score recompute
  21. 2026-06-23 23:33 UTCEG score recompute
  22. 2026-06-23 21:33 UTCEPSS rescore
  23. 2026-06-23 21:33 UTCEPSS rescore
  24. 2026-06-23 12:34 UTCEG score recompute
  25. 2026-06-23 01:19 UTCEG score recompute
  26. 2026-06-22 14:22 UTCEG score recompute
  27. 2026-06-22 03:25 UTCEG score recompute
  28. 2026-06-21 15:32 UTCEG score recompute
  29. 2026-06-21 04:34 UTCEG score recompute
  30. 2026-06-20 17:28 UTCEG score recompute
  31. 2026-06-20 06:30 UTCEG score recompute
  32. 2026-06-19 19:29 UTCEG score recompute
  33. 2026-06-19 08:33 UTCEG score recompute
  34. 2026-06-18 21:35 UTCEG score recompute
  35. 2026-06-18 10:39 UTCEG score recompute
  36. 2026-06-17 23:37 UTCEG score recompute
  37. 2026-06-17 12:41 UTCEG score recompute
  38. 2026-06-17 01:43 UTCEG score recompute
  39. 2026-06-16 14:46 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54290?
CVE-2026-54290 is a high vulnerability published on June 16, 2026. Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.25, with credentials: true and no explicit origin (the default wildcard), the CORS Middleware reflects the request's Origin and sends Access-Control-Allow-Credentials: true. Any site can then make…
When was CVE-2026-54290 disclosed?
CVE-2026-54290 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54290 actively exploited?
CVE-2026-54290 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54290?
CVE-2026-54290 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-54290?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54290, 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-54290

Explore →

Is Your Infrastructure Affected by CVE-2026-54290?

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

Start Free Scan →Browse All CVEs