Validation bypass in Hono form validator for multipart requests
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub.
Summary
Hono from 4.5.1 before 4.13.16 is affected. Its validator('form') uses a strict header pattern that fails to recognize multipart/form-data when the Content-Type has an extra parameter or extra whitespace after a semicolon, so the validation callback receives an empty object (CWE-20 Improper Input Validation). An unauthenticated remote client can bypass allow-list or required-field checks when the application relies on this validator and its callback accepts an empty object.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the CNA
Hono is a Web application framework that provides support for any JavaScript runtime. From 4.5.1 until 4.13.16, validator('form') uses a strict whole-header pattern that fails to recognize multipart/form-data when its Content-Type includes another legal parameter or extra whitespace after a semicolon. The validation callback receives an empty object even though c.req.parseBody() or c.req.formData() can still parse and expose all submitted fields to the handler. An unauthenticated client can therefore bypass allow-list or required-field checks when the application relies on the form validator and its callback accepts an empty object. application/x-www-form-urlencoded requests are not affected. This issue is fixed in version 4.13.16.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| honojs | hono | 4.5.1 to before 4.13.16 | 4.13.16 | Patch available | CNA |
| — | hono (npm) | 4.5.1 to before 4.13.16 | 4.13.16 | Patch available | GHSA-4h7h-rv7c-7m2v |
- hono Vendorhonojs Affected 4.5.1 to before 4.13.16 Fixed in 4.13.16 Patch available CNA
- hono (npm) Vendor— Affected 4.5.1 to before 4.13.16 Fixed in 4.13.16 Patch available GHSA-4h7h-rv7c-7m2v
Remediation
Upgrade the hono package to version 4.13.16, which fixes the issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
- Fix · CNA hono (honojs) Fixed in 4.13.16
- Fix · GHSA-4h7h-rv7c-7m2v hono (npm) Fixed in 4.13.16 Advisory →
Timeline
- 2026-11-12 Threatist record created from CVE-2026-126356
- 2026-11-13 Alias added: GHSA-4h7h-rv7c-7m2v
- 2026-11-13 Fix available: npm/[email protected] · GHSA-4h7h-rv7c-7m2v
- 2026-11-13 CVSS score added · GHSA-4h7h-rv7c-7m2v
- 2026-11-13 Weakness changed · GHSA-4h7h-rv7c-7m2v
- 2026-11-13 4 new references · GHSA-4h7h-rv7c-7m2v
- 2026-11-13 CISA SSVC decision points changed
References
More honojs vulnerabilities
- TI-2024-21741 Hono vulnerable to Restricted Directory Traversal in serveStatic with deno CVSS 3.1MEDIUM 5.3
- TI-2024-15441 @hono/node-server can't handle "double dots" in URL CVSS 3.1MEDIUM 5.3
- TI-2024-32610 Hono vulnerable to bypass of CSRF Middleware by a request without Content-Type header. CVSS 3.1MEDIUM 5.9
- TI-2024-29381 Hono CSRF middleware can be bypassed using crafted Content-Type header CVSS 3.1MEDIUM 5.0
- TI-2026-39189 Hono: Lambda@Edge adapter keeps only the last value of a repeated request header, dropping the rest CVSS 3.1MEDIUM 4.8
- TI-2026-23190 Hono: Arbitrary file access via serveStatic vulnerability CVSS 3.1CRITICAL 9.8
Sources
- CVE-2026-126356 · CVE Program
- CVE-2026-126356 · NVD
- FIRST EPSS
- GHSA-4h7h-rv7c-7m2v · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences