CVE-2026-84364: Hono: Unbounded dot-notation nesting in `parseBody()` can cause memory exhaustion
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.
Published Sep 8, 2026
Affected packages
hono
- Ecosystem
- npm
- Affected
- < 4.13.5
- Fixed in
- 4.13.5
- Check
npm ls hono
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to Rikuxx0.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-126355
Hono: `csrf()` does not check requests sent by hyperlink auditing (`text/ping`)
medium5.3Nov 12, 2026CVE-2026-126356
Hono: `validator('form')` skips validation for `multipart/form-data` requests with extra parameters
medium5.3Nov 12, 2026CVE-2026-126357
Hono: `mount()` and `app.mount()` can forward a path that bypasses middleware scoped inside the mount prefix
medium5.3Nov 12, 2026CVE-2026-126358
Hono: RegExpRouter skips wildcard middleware for some route sets and for paths with an encoded line terminator
medium5.3Nov 12, 2026CVE-2026-126359
Hono: `css` helper does not escape a closing tag split between the template and an interpolated value, allowing HTML injection
low3.4Nov 12, 2026CVE-2026-111757
Hono: `serveStatic` decodes the request path a second time, leading to bypass of middleware on static paths
medium5.3Oct 20, 2026
