Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-29085: CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') in honojs hono

0
Medium
VulnerabilityCVE-2026-29085cvecve-2026-29085cwe-74
Published: Wed Mar 04 2026 (03/04/2026, 22:09:45 UTC)
Source: CVE Database V5
Vendor/Project: honojs
Product: hono

Description

Hono is a Web application framework that provides support for any JavaScript runtime. Prior to version 4.12.4, when using streamSSE() in Streaming Helper, the event, id, and retry fields were not validated for carriage return (\r) or newline (\n) characters. Because the SSE protocol uses line breaks as field delimiters, this could allow injection of additional SSE fields within the same event frame if untrusted input was passed into these fields. This issue has been patched in version 4.12.4.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/04/2026, 22:33:28 UTC

Technical Analysis

CVE-2026-29085 is a vulnerability classified under CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component) affecting the honojs web application framework before version 4.12.4. The issue lies in the streamSSE() function of the Streaming Helper, which handles Server-Sent Events (SSE). Specifically, the event, id, and retry fields are not properly validated against carriage return (\r) or newline (\n) characters. Since the SSE protocol uses line breaks as delimiters between fields, an attacker can inject additional SSE fields within the same event frame by including these special characters in untrusted input. This injection can manipulate the event stream, potentially causing downstream components or clients to process malicious or altered data. The vulnerability can be exploited remotely without authentication or user interaction, increasing its risk profile. The flaw was patched in hono version 4.12.4 by adding proper validation to these fields to reject or sanitize carriage return and newline characters. No known exploits have been reported in the wild, but the vulnerability’s CVSS score of 6.5 reflects a medium severity due to its potential impact on confidentiality and integrity without affecting availability.

Potential Impact

The primary impact of CVE-2026-29085 is on the integrity and confidentiality of data transmitted via Server-Sent Events in applications using the vulnerable honojs versions. An attacker who can supply untrusted input to the event, id, or retry fields can inject additional SSE fields, potentially manipulating event streams to deliver malicious payloads or disrupt expected client behavior. This can lead to unauthorized data disclosure or corruption of real-time event data, undermining trust in the application’s communication channel. Since SSE is often used for real-time notifications, updates, or streaming data, exploitation could affect user experience and application correctness. The vulnerability does not impact availability directly but could be leveraged as part of a broader attack chain. Organizations relying on honojs for critical real-time web services may face reputational damage and operational risks if exploited.

Mitigation Recommendations

To mitigate CVE-2026-29085, organizations should upgrade all honojs deployments to version 4.12.4 or later, where the vulnerability is patched. Until upgrades are applied, developers should implement strict input validation and sanitization on all data passed into the event, id, and retry fields of the streamSSE() function, explicitly disallowing carriage return (\r) and newline (\n) characters. Employing a whitelist approach for allowed characters in these fields can reduce injection risk. Additionally, monitoring and logging SSE traffic for anomalous or unexpected field values can help detect exploitation attempts. Security teams should review application code to ensure no other SSE-related injection vectors exist and consider applying web application firewalls (WAFs) with custom rules to block suspicious SSE payloads. Regularly auditing dependencies and staying current with honojs releases will reduce exposure to similar vulnerabilities.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-03T20:51:43.484Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69a8afacd1a09e29cb7ac721

Added to database: 3/4/2026, 10:18:20 PM

Last enriched: 3/4/2026, 10:33:28 PM

Last updated: 4/18/2026, 1:00:02 AM

Views: 67

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses