Description
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.13.5, when parseBody() expands dot-separated form field names into nested objects with dot-notation parsing enabled, it does not limit the nesting depth or the total number of intermediate objects created. Empty segments are preserved, so one deeply dotted field name can encode one nesting level per byte, while a large number of shallowly dotted fields can create the same amplification across a request. A request body within a normal size limit can therefore allocate an object graph far larger than the request after the body has already been accepted. An unauthenticated attacker who can reach an affected endpoint can send concurrent requests that exhaust the JavaScript heap, terminate the server process, and leave the service unavailable until restart. Dot-notation parsing is not enabled by default, and applications using the default behavior are not affected. This issue is fixed in version 4.13.5.
Published: 2026-09-01
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service (Memory Exhaustion)
Action: Apply Patch
AI Analysis

Impact

Hono, a JavaScript web framework, contains a flaw in the parseBody() method when dot-notation parsing is enabled: the framework does not cap the depth of nested objects derived from dotted field names. An attacker can craft a single request body with many deeply nested or numerous dotted fields, causing the server to allocate a vastly larger object graph than the original payload. The resulting exhaustion of the JavaScript heap can terminate the process, leaving the service unavailable until a restart.

Affected Systems

Versions of Hono prior to 4.13.5 that use parseBody() with dot-notation parsing enabled are impacted. By default, dot-notation is disabled, so applications that have not explicitly enabled it remain safe. Configurations that set dot-notation to true or rely on the framework's default parsing will be vulnerable.

Risk and Exploitability

The CVSS score of 5.3 classifies this vulnerability as moderate severity. The EPSS score is not provided, but the scenario requires an unauthenticated attacker able to reach a vulnerable endpoint and send concurrent requests. Successful exploitation results in a denial of service due to heap exhaustion. The vulnerability is not listed in CISA's KEV catalog, indicating no identified large-scale exploitation yet.

Generated by OpenCVE AI on September 2, 2026 at 02:57 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Hono to version 4.13.5 or later
  • Disable dot-notation parsing for parseBody if it is not required by the application
  • Configure request size limits or rate limiting to reduce memory consumption during parsing

Generated by OpenCVE AI on September 2, 2026 at 02:57 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-g6gw-c38x-mqfc Hono: Unbounded dot-notation nesting in `parseBody()` can cause memory exhaustion
History

Thu, 03 Sep 2026 09:30:00 +0000

Type Values Removed Values Added
First Time appeared Hono
Hono hono
Vendors & Products Hono
Hono hono

Wed, 02 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 01 Sep 2026 22:00:00 +0000

Type Values Removed Values Added
Description Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.13.5, when parseBody() expands dot-separated form field names into nested objects with dot-notation parsing enabled, it does not limit the nesting depth or the total number of intermediate objects created. Empty segments are preserved, so one deeply dotted field name can encode one nesting level per byte, while a large number of shallowly dotted fields can create the same amplification across a request. A request body within a normal size limit can therefore allocate an object graph far larger than the request after the body has already been accepted. An unauthenticated attacker who can reach an affected endpoint can send concurrent requests that exhaust the JavaScript heap, terminate the server process, and leave the service unavailable until restart. Dot-notation parsing is not enabled by default, and applications using the default behavior are not affected. This issue is fixed in version 4.13.5.
Title Hono: Unbounded dot-notation nesting in `parseBody()` can cause memory exhaustion
Weaknesses CWE-400
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-02T15:45:34.325Z

Reserved: 2026-09-01T16:27:58.128Z

Link: CVE-2026-84364

cve-icon Vulnrichment

Updated: 2026-09-02T15:45:31.537Z

cve-icon NVD

Status : Deferred

Published: 2026-09-01T21:18:47.317

Modified: 2026-09-09T21:09:13.080

Link: CVE-2026-84364

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-02T22:10:17Z

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption