# CVE-2024-48913: Hono vulnerable to bypass of CSRF Middleware by a request without Content-Type header.

> Attackers can bypass CSRF protection in the Hono web framework by sending requests without a Content-Type header, allowing unauthorized state-changing actions.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/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
- **Fix available:** Yes
- **Published:** 15 Oct 2024
- **Updated:** 7 Nov 2024
- **Also known as:** GHSA-2234-fmw7-43wr, MINI-v678-9c6f-pvw5

## What is CVE-2024-48913?

CVE-2024-48913 is a medium-severity vulnerability in honojs hono, published on 15 Oct 2024. 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, a web framework, prior to version 4.6.5 is vulnerable to bypass of cross-site request forgery (CSRF) middleware by a request without Content-Type header. Although the CSRF middleware verifies the Content-Type Header, Hono always considers a request without a Content-Type header to be safe. This can allow an attacker to bypass CSRF protection implemented with Hono CSRF middleware. Version 4.6.5 fixes this issue.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-48913?

2 open source packages ship an affected version, including hono. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hono` | npm | All versions | 4.6.5 |
| `hono` | npm | All versions | 4.6.5 |

Products: Hono Hono.

## How do I fix CVE-2024-48913?

Upgrade hono to 4.6.5 or later.

## Is CVE-2024-48913 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48913 exists.

## Other vulnerabilities in honojs hono

- [CVE-2026-27700](https://insights.sbomify.com/CVE-2026-27700/): Hono is Vulnerable to Authentication Bypass by IP Spoofing in AWS Lambda ALB conninfo (high 8.2)
- [CVE-2026-22817](https://insights.sbomify.com/CVE-2026-22817/): JWT Algorithm Confusion via Unsafe Default (HS256) in Hono JWT Middleware Allows Token Forgery and Auth Bypass (high 8.2)
- [CVE-2026-22818](https://insights.sbomify.com/CVE-2026-22818/): JWT algorithm confusion in Hono JWK Auth Middleware when JWK lacks "alg" (untrusted header.alg fallback) (high 8.2)
- [CVE-2025-62610](https://insights.sbomify.com/CVE-2025-62610/): Hono Improperly Authorizes JWT Audience Validation (high 8.1)
- [CVE-2026-29045](https://insights.sbomify.com/CVE-2026-29045/): Hono: Arbitrary file access via serveStatic vulnerability (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-48913 and fix it if it is affected.

What it is: CVE-2024-48913 is a medium-severity vulnerability in honojs hono, published on 15 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48913 exists.

Affected packages and fixed versions:
- hono (npm): affected all versions; fixed in 4.6.5
- hono (npm): affected all versions; fixed in 4.6.5

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.
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-2024-48913/ (Markdown: https://insights.sbomify.com/CVE-2024-48913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-48913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-48913
- OSV: https://osv.dev/vulnerability/CVE-2024-48913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-48913/
Summaries are generated and may contain mistakes; the official description above is the record.