CVE-2026-84364: Hono: Unbounded dot-notation nesting in `parseBody()` can cause memory exhaustion
Medium CVSS 5.3
- OSV id
- GHSA-g6gw-c38x-mqfc
- Also known as
- CVE-2026-84364
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| hono npm |
< 4.13.5 | 4.13.5 |
Versions we track that it affects: hono 4.13.3
How to fix it
Upgrade hono to 4.13.5 or later.
npm install hono@4.13.5
# if it is an indirect dependency: npm update hono (or npm audit fix)
- If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
Summary
When parseBody() expands dot-separated form field names into nested objects, it does not limit the nesting depth or the total number of objects created. A request body well within a normal size limit can therefore allocate an object graph far larger than the request itself, and concurrent requests can exhaust the heap and terminate the process.
Details
Each dot-separated segment of a field name creates an intermediate object. Neither the segments within a single field name nor the total across a request was bounded, and empty segments were preserved, so a field name could encode one nesting level per byte.
Both shapes produce the effect: a single deeply dotted field name, and a large number of shallowly dotted ones within one body. A request body size limit does not prevent it, because the amplification happens after the body has been accepted.
Dot-notation parsing is not enabled by default.
Impact
An attacker who can reach an endpoint that parses request bodies with dot-notation enabled can send concurrent requests whose memory cost is disproportionate to their size.
This may lead to:
- exhaustion of the JavaScript heap and termination of the server process
- the service remaining unavailable until it is restarted
This issue affects applications that explicitly enable dot-notation parsing. Applications using the default behaviour are not affected.
References
- GHSA-g6gw-c38x-mqfc on OSV.dev
- Web: https://github.com/honojs/hono/security/advisories/GHSA-g6gw-c38x-mqfc
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-84364
- Web: https://github.com/honojs/hono/commit/531e9c5a3ae058d10de33f643055bd4009a87178
- Package: https://github.com/honojs/hono
- Web: https://github.com/honojs/hono/releases/tag/v4.13.5
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.