Vulnerability · Published Sep 16, 2026 · Assigned by GitHub_M

CVE-2026-68904node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion

High 7.0

In plain English

A high-severity uncontrolled resource consumption in node-opcua from node-opcua. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 39% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.0High
Exploit odds (30 days)0.4%top 61.3% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

node-opcua is an OPC UA implementation for TypeScript and Node.js. From 2.0.0 until 2.170.0, node-opcua clients using the default keepSessionAlive setting can enter a repeated reconnection cycle when an OPC UA server's clock skew causes BadInvalidTimestamp responses. ClientSessionKeepAliveManager._ping_server treated the server-originated ServiceFault as a network outage and forced a transport reconnect, while ClientTCP_transport._on_ACK_response used socket.end() after failed HEL/ACK negotiation and could leave the connection in FIN-WAIT-2 when the peer did not close. Repetition at the keepAliveInterval accumulates file descriptors and memory until the client process or container can be terminated by resource exhaustion. This issue is fixed in version 2.170.0.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
npmnode-opcua2.170.0GHSA-r2pf-9cw4-5j65
npmnode-opcua-client2.170.0GHSA-r2pf-9cw4-5j65
npmnode-opcua-transport2.170.0GHSA-r2pf-9cw4-5j65

Affected products (as reported)

VendorProductVersions
node-opcua node-opcua >= 2.0.0, < 2.170.0

Weakness: CWE-400 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H

References