Skip to content

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

HighCVSS 7.0 EPSS 0.44%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial

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.

Upgrade path

4 packages: 3 fixed.

PackageAffectedFixed inStatus
npm node-opcua(npm) >= 2.0.0, < 2.170.0 2.170.0 Fixed
npm node-opcua-client(npm) >= 2.0.0, < 2.170.0 2.170.0 Fixed
npm node-opcua-transport(npm) >= 2.0.0, < 2.170.0 2.170.0 Fixed
node-opcua = >= 2.0.0, < 2.170.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
node-opcua = >= 2.0.0, < 2.170.0 No fix listed
npm node-opcua-transport(npm) >= 2.0.0, < 2.170.0 2.170.0
npm node-opcua-client(npm) >= 2.0.0, < 2.170.0 2.170.0
npm node-opcua(npm) >= 2.0.0, < 2.170.0 2.170.0

References