CVE-2026-126355: Hono · `csrf()` does not check requests sent by hyperlink auditing (`text/ping`)
Affects honoSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 4.13.16 when convenient.
Data as of 13 Nov 2026, 00:08 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 4.13.16
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 12 Nov 2026.
What to do
Upgrade hono to 4.13.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmhono | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in hono version 4.13.16. Until patched, applications can mitigate this issue by rejecting requests with Content-Type 'text/ping' in middleware registered before csrf(), or by setting session cookies with SameSite=Strict. Users should upgrade to hono 4.13.16 or later to fully remediate the vulnerability.
Description
The hono framework's csrf() middleware does not validate requests with the Content-Type 'text/ping', which are sent by Chromium-based browsers' hyperlink auditing feature. This allows cross-origin POST requests with user cookies to bypass CSRF protections if the state-changing action does not depend on the request body. The vulnerability affects hono versions prior to 4.13.16.