Read the docs

Hono csrf() does not check hyperlink auditing (text/ping) requests

Priority LOW 23CWE-352Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
High
Impact type
Tampering
Confidentiality · integrity · availability
None · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-352.

Summary

Hono versions before 4.13.16 do not validate cross-origin requests sent by Chromium hyperlink auditing (text/ping) in the csrf() middleware. Because the middleware limits origin checks to content types sent by HTML forms, Chrome and Edge can send a credentialed cross-site POST through an anchor ping action, and the Origin and Sec-Fetch-Site checks are skipped. An attacker can exploit this against state-changing endpoints whose effect depends only on the path or query string, when the victim's cookie is sent with the request, which generally requires a same-site origin or SameSite=None. This is tracked as CWE-352 (Cross-Site Request Forgery).

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.13.16, csrf() limits origin validation to the content types normally sent by HTML forms and therefore does not validate text/ping requests generated by Chromium hyperlink auditing. Chrome and Edge can send a cross-origin credentialed POST without a CORS preflight through an <a ping> action, and the middleware then skips both Origin and Sec-Fetch-Site checks. The fixed request body limits exploitation to state-changing endpoints whose effect is selected by the path or query string and does not depend on submitted body data. The user's cookie must accompany the request, which generally requires a same-site origin or a cookie configured with SameSite=None, and Firefox does not send hyperlink-auditing pings by default. This issue is fixed in version 4.13.16.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00176 7th percentileScored 2026-11-16
Fix Fixed hono (honojs): 4.13.16hono (npm): 4.13.16

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
honojshonobefore 4.13.164.13.16Patch availableCNA
—hono (npm)before 4.13.164.13.16Patch availableGHSA-46wx-v44x-9hh2
  • hono Vendorhonojs Affected before 4.13.16 Fixed in 4.13.16 Patch available CNA
  • hono (npm) Vendor— Affected before 4.13.16 Fixed in 4.13.16 Patch available GHSA-46wx-v44x-9hh2

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:hono:hono:*:*:*:*:*:*:*:*——honojs
  • cpe:2.3:a:hono:hono:*:*:*:*:*:*:*:* Versions — — ·honojs

Remediation

Upgrade hono to version 4.13.16, which fixes the issue in the npm package hono.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA hono (honojs) Fixed in 4.13.16
  • Fix · GHSA-46wx-v44x-9hh2 hono (npm) Fixed in 4.13.16 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from CVE-2026-126355
  2. 2026-11-13 Alias added: GHSA-46wx-v44x-9hh2
  3. 2026-11-13 Fix available: npm/[email protected] · GHSA-46wx-v44x-9hh2
  4. 2026-11-13 CVSS score added · GHSA-46wx-v44x-9hh2
  5. 2026-11-13 Weakness changed · GHSA-46wx-v44x-9hh2
  6. 2026-11-13 4 new references · GHSA-46wx-v44x-9hh2
  7. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2024-21741 Hono vulnerable to Restricted Directory Traversal in serveStatic with deno CVSS 3.1MEDIUM 5.3
  • TI-2024-15441 @hono/node-server can't handle "double dots" in URL CVSS 3.1MEDIUM 5.3
  • TI-2024-32610 Hono vulnerable to bypass of CSRF Middleware by a request without Content-Type header. CVSS 3.1MEDIUM 5.9
  • TI-2024-29381 Hono CSRF middleware can be bypassed using crafted Content-Type header CVSS 3.1MEDIUM 5.0
  • TI-2026-39189 Hono: Lambda@Edge adapter keeps only the last value of a repeated request header, dropping the rest CVSS 3.1MEDIUM 4.8
  • TI-2026-23190 Hono: Arbitrary file access via serveStatic vulnerability CVSS 3.1CRITICAL 9.8
See all 67 →

Sources