Skip to main content
VulnerabilityPublished

CVE-2026-59895: honojs hono · Cross-site Scripting

Affects honojs honoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 4.12.27 when convenient.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 3.1 base score
6.1Medium
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.27
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 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 21 Nov 2026.

What to do

Upgrade honojs hono to 4.12.27.

Affected software

ProductAffectedFixed in
honojshonoAffected
  • >=4.0.0 <4.12.27
Fixed in
  • 4.12.27
npmhonopkg:npm/honoOther threatsAffected
  • >=4.0.0 <4.12.27
Fixed in
  • 4.12.27

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

AI-suggested

Upgrade to hono version 4.12.27 or later, where this vulnerability is fixed. No other official remediation or temporary fixes are documented. Patch status is confirmed by the vendor advisory stating the issue is fixed in 4.12.27.

Description

A cross-site scripting (XSS) vulnerability exists in honojs hono versions from 4.0.0 up to but not including 4.12.27. The cx() function in hono/css composes class names from plain strings but marks them as already escaped without properly HTML-escaping input. This allows untrusted className values used in JSX class attributes during server-side rendering to inject arbitrary markup. The issue is fixed in version 4.12.27.

References

Community reviews

Loading reviews…