Skip to main content
VulnerabilityPublished

CVE-2026-54290: honojs hono · Permissive Cross-domain Policy with Untrusted Domains

Affects honojs honoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 4.12.25 soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.12.25
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade honojs hono to 4.12.25.

Affected software

ProductAffectedFixed in
honojshonoAffected
  • <4.12.25
Fixed in
  • 4.12.25
npmhonopkg:npm/honoOther threatsAffected
  • <4.12.25
Fixed in
  • 4.12.25

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade hono to version 4.12.25 or later, where this vulnerability is fixed. There is no official remediation level stated beyond this fix. Patch status is confirmed by the version update. Until patched, avoid using credentials: true with the default wildcard origin in CORS middleware configurations.

Description

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.

References

Community reviews

Loading reviews…