# CVE-2026-126355: Hono: `csrf()` does not check requests sent by hyperlink auditing (`text/ping`) > Attackers can bypass Hono's CSRF protection using text/ping requests to change state on endpoints; Hono app developers should care. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Harmful if only installed:** No - **Needs a specific call:** Yes (`csrf()`) - **Fix available:** Yes - **Published:** 12 Nov 2026 - **Updated:** 12 Nov 2026 - **Also known as:** GHSA-46wx-v44x-9hh2 ## What is CVE-2026-126355? CVE-2026-126355 is a medium-severity cross-site request forgery vulnerability in honojs hono, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official 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 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. Weakness: CWE-352 (Cross-Site Request Forgery) ## Which versions are affected by CVE-2026-126355? 1 open source package ship an affected version, including hono. An affected version is only exploitable if your software calls csrf(). Many projects that include it are not exposed. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `hono` | npm | All versions | 4.13.16 | ## How do I fix CVE-2026-126355? Upgrade hono to 4.13.16 or later. ## Is CVE-2026-126355 being exploited? There is no known exploitation of CVE-2026-126355 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-126355 and fix it if it is affected. What it is: CVE-2026-126355 is a medium-severity cross-site request forgery vulnerability in honojs hono, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-126355 in the wild and no public exploit code. Exposure: An affected version is only exploitable if your software calls csrf(). Many projects that include it are not exposed. Affected packages and fixed versions: - hono (npm): affected all versions; fixed in 4.13.16 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. If an affected version is present, also search the code for calls to csrf() and report whether any exist. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-126355/ (Markdown: https://insights.sbomify.com/CVE-2026-126355/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126355 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126355 - OSV: https://osv.dev/vulnerability/CVE-2026-126355 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-126355/ Summaries are generated and may contain mistakes; the official description above is the record.