Answer in brief
CVE-2026-68904 records a High severity (CVSS 7.0) vulnerability in node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion. The current sources do not mark it as known exploited. The current feed maps node-opcua/node-opcua (generic), node-opcua (npm), node-opcua-client (npm), node-opcua-transport (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps node-opcua/node-opcua (generic), node-opcua (npm), node-opcua-client (npm), node-opcua-transport (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| node-opcua/node-opcuageneric | >= 2.0.0, < 2.170.0 | Not reported |
| node-opcuanpm | >=2.0.0,<2.170.0 | 2.170.0 |
| node-opcua-clientnpm | >=2.0.0,<2.170.0 | 2.170.0 |
| node-opcua-transportnpm | >=2.0.0,<2.170.0 | 2.170.0 |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.