Bug 2572853 (CVE-2026-126356)
| Summary: | CVE-2026-126356 hono: Hono: Form validation bypass via crafted Content-Type header | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | dhanak, drosa, dsimansk, dymurray, jlanda, jwong, kingland, kshier, lchilton, mnovotny, rbobbitt, rhel-process-autobot, sausingh, sdawley, sfeifer, simaishi, stcannon, tguha, watson-tool-maintainers, yguenane |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: |
A flaw was found in Hono. A remote, unauthenticated attacker can bypass application input validation by submitting a multipart form request containing extra parameters or whitespace in the Content-Type header. Because the framework's form validator fails to recognize these headers, it skips validation checks while the application continues to parse and process the submitted data. Consequently, an attacker can bypass required-field and allowlist controls, allowing unvalidated input to reach application handlers.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2578334 | ||
| Bug Blocks: | |||
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.