CVSS 3.1
5.3 mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:NCVE-2026-126355
Hono: `csrf()` does not check requests sent by hyperlink auditing (`text/ping`)
Medium (5.3) in honojs hono. Fixed in hono 4.13.16.
On this page
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.
Severity
- CWE
- CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Not in the NVD yet
- Record from
- the CVE List, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-126355 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126355?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126355?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126355 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-126355)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126355"><img src="https://cve.bz/cve/badge/CVE-2026-126355.svg" alt="CVE-2026-126355"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| honojs hono | < 4.13.16 |
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-46wx-v44x-9hh2 | npm | hono | <4.13.16 | 4.13.16 |
Attack patterns (CAPEC)
- CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
- CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
- CAPEC-462 Cross-Domain Search Timing Severity: Medium
- CAPEC-467 Cross Site Identification Severity: Low
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.