# CVE-2024-32869: Hono vulnerable to Restricted Directory Traversal in serveStatic with deno

> Attackers can traverse directories to read unexpected files when using serveStatic with Deno in the Hono web framework.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-3mpf-rcc7-5347

## What is CVE-2024-32869?

CVE-2024-32869 is a medium-severity path traversal vulnerability in honojs hono, published on 23 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hono is a Web application framework that provides support for any JavaScript runtime. Prior to version 4.2.7, when using serveStatic with deno, it is possible to traverse the directory where `main.ts` is located. This can result in retrieval of unexpected files. Version 4.2.7 contains a patch for the issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


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

Products: Hono Hono.

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

Upgrade hono to 4.2.7 or later.

## Is CVE-2024-32869 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32869 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-32869 and fix it if it is affected.

What it is: CVE-2024-32869 is a medium-severity path traversal vulnerability in honojs hono, published on 23 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32869 exists.

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

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

## Sources

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

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