CVE
Hono request forgery bypass in CSRF middleware
- Exploited
- No known exploitation
- Fix
- Fixed in 4.13.16
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.13.16.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.18% · 7th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 32/100 · provisional
- The share of the registry's downloads of each affected package in the window that were versions inside the affected ranges. Downloads, not users or installs: CI runs and mirrors inflate the counts.
- 80% of hono downloads last week were affected versions (83.8M).npm, 105.3M downloads in the last 7 days, read Nov 8, 2026
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Hono's `csrf()` middleware does not check POST requests sent through browser hyperlink auditing (`text/ping`), so those requests skip both its Origin and Sec-Fetch-Site checks. A remote attacker without a login could, by getting a user to click a crafted link in Chrome or Edge, make the user's browser send a cross-origin POST that changes state on endpoints selected by path or query string, though the user's cookie must accompany the request.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach20/20hono: 104.5M downloads a week
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 87 if added to CISA KEV
- Would score about 82 if CISA's SSVC rates exploitation active
- Would score about 47 if advisories confirm default setups are exposed
Impact
What to do
Upgrade to a fixed version: 4.13.16.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126355 (Hono: `csrf()` does not check requests sent by hyperlink auditing (`text/ping`)), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126355 (entry last updated 2026-11-12):
Affected:
- honojs hono: fixed in 4.13.16
- npm package hono: fixed in 4.13.16
Fixed versions: 4.13.16.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126355 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126355 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/honojs/hono/security/advisories/GHSA-46wx-v44x-9hh2
- https://github.com/honojs/hono/commit/bf16471913b5199212dac33f5d170f94745dd26a
- https://github.com/honojs/hono/releases/tag/v4.13.16
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126355
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126355"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- honojs hono
fixed in 4.13.16
- hononpm
fixed in 4.13.16
Fixed in 4.13.16 (released Nov 1, 2026, 11 days before disclosure).
The latest release, 4.13.17, is not affected.
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126355
Is CVE-2026-126355 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-126355?
hono: before 4.13.16. hono (npm): before 4.13.16.Source: cve.now feed data
How do I fix CVE-2026-126355?
Upgrade to a fixed version: 4.13.16.Source: cve.now feed data