CVE-2026-47675: CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') in honojs hono
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, the serialize() function in hono/cookie validates domain and path options against characters that corrupt Set-Cookie header syntax (;, \r, \n), but does not apply the same validation to sameSite and priority. An application that passes user-controlled input into either option may produce a Set-Cookie response header containing attacker-chosen additional attributes. This vulnerability is fixed in 4.12.21.
AI Analysis
Technical Summary
The vulnerability in honojs hono (before 4.12.21) involves improper neutralization of CRLF sequences in HTTP headers, specifically in the serialize() function used for cookie handling. While domain and path options are validated to prevent injection of characters like ';', '\r', and '\n', the sameSite and priority options lack this validation. This can lead to HTTP response splitting by allowing attacker-controlled input to inject additional Set-Cookie attributes. The issue is addressed in version 4.12.21.
Potential Impact
An attacker who can control input passed to the sameSite or priority options in the serialize() function may cause the application to generate a Set-Cookie header with injected attributes. This can lead to HTTP response splitting attacks, potentially allowing header injection or manipulation of cookie attributes. The CVSS score of 4.3 reflects a medium impact with limited integrity impact and no confidentiality or availability impact.
Mitigation Recommendations
Upgrade the honojs hono framework to version 4.12.21 or later, where this vulnerability is fixed. There is no vendor advisory explicitly provided, but the description confirms the fix in 4.12.21. Until upgrading, avoid passing user-controlled input to the sameSite and priority options in cookie serialization.
CVE-2026-47675: CWE-113: Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') in honojs hono
Description
Hono is a Web application framework that provides support for any JavaScript runtime. Prior to 4.12.21, the serialize() function in hono/cookie validates domain and path options against characters that corrupt Set-Cookie header syntax (;, \r, \n), but does not apply the same validation to sameSite and priority. An application that passes user-controlled input into either option may produce a Set-Cookie response header containing attacker-chosen additional attributes. This vulnerability is fixed in 4.12.21.
CVSS v3.1
Score 4.3medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in honojs hono (before 4.12.21) involves improper neutralization of CRLF sequences in HTTP headers, specifically in the serialize() function used for cookie handling. While domain and path options are validated to prevent injection of characters like ';', '\r', and '\n', the sameSite and priority options lack this validation. This can lead to HTTP response splitting by allowing attacker-controlled input to inject additional Set-Cookie attributes. The issue is addressed in version 4.12.21.
Potential Impact
An attacker who can control input passed to the sameSite or priority options in the serialize() function may cause the application to generate a Set-Cookie header with injected attributes. This can lead to HTTP response splitting attacks, potentially allowing header injection or manipulation of cookie attributes. The CVSS score of 4.3 reflects a medium impact with limited integrity impact and no confidentiality or availability impact.
Mitigation Recommendations
Upgrade the honojs hono framework to version 4.12.21 or later, where this vulnerability is fixed. There is no vendor advisory explicitly provided, but the description confirms the fix in 4.12.21. Until upgrading, avoid passing user-controlled input to the sameSite and priority options in cookie serialization.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-19T21:10:38.798Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1871ece29bf47b501245a0
Added to database: 5/28/2026, 4:48:44 PM
Last enriched: 5/28/2026, 5:04:33 PM
Last updated: 5/29/2026, 4:25:37 PM
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.