CVE-2026-126343VulnerabilityPublished 12 Nov 2026

@hono/node-server: Unhandled `ECONNRESET` on the socket during an asynchronous WebSocket upgrade crashes the process

Affects @hono/node-serverSource GCVE Database

Compare

Authoritative record:CVE-2026-126343· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.1.6 when convenient.

Data as of 12 Nov 2026, 22:23 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (GitHub_M)	CVSS 3.1	5.3

Patch: Available – fixed in 2.1.6

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade @hono/node-server to 2.1.6.

Affected software

Product	Affected	Fixed in
npm@hono/node-server	Affected >=2.0.0 <2.1.6	Fixed in 2.1.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to @hono/node-server version 2.1.6 or later, where the issue is fixed by attaching error and close listeners to the socket before application handling. This prevents unhandled ECONNRESET errors and properly releases pending upgrades. No other mitigation is required.

Description

A vulnerability in @hono/node-server versions >=2.0.0 and <2.1.6 allows an unauthenticated client to crash the server process by sending a WebSocket upgrade request and resetting the TCP connection before the application responds. This occurs because the socket lacks an error listener during asynchronous middleware execution, causing an unhandled ECONNRESET error that terminates the process. The issue is fixed in version 2.1.6.

Impact

An unauthenticated attacker can cause a denial of service by crashing the server process with a single specially crafted WebSocket upgrade request followed by a connection reset. If the crash is suppressed by global error handlers, repeated exploitation can cause memory exhaustion due to unreleased pending upgrades. This affects applications using WebSocket support in @hono/node-server with asynchronous middleware on the upgrade path.

Summary

@hono/node-server's WebSocket upgrade handler awaits the application response before attaching error listeners to the socket. If a client resets the TCP connection during this asynchronous wait, an unhandled 'error' event with ECONNRESET is emitted, crashing the server process. If a global uncaughtException handler swallows this error, the pending upgrade remains unreleased, causing memory growth. The fix involves attaching error and close listeners to the socket before calling the application, releasing pending upgrades on socket close, and skipping handshake on destroyed sockets.

CWE-248Uncaught Exception (opens in a new tab)
Base weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
An exception is thrown from a function, but it is not caught.
Requirements
The choice between a language which has named or unnamed exceptions needs to be done. While unnamed exceptions exacerbate the chance of not properly dealing with an exception, named exceptions suffer from the up call version of the weak base class problem.
Requirements
A language can be used which requires, at compile time, to catch all serious exceptions. However, one must make sure to use the most current version of the API as new exceptions could be added.
Implementation
Catch all relevant exceptions. This is the recommended solution. Ensure that all exceptions are handled in such a way that you can be sure of the state of your system at any given moment.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Nov 2026, 22:23 UTC

WeaknessesCWE-248

Technical details

References

Community reviews

Related threats