p PatchFirst

CVE-2026-68904

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

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 7.0 · High · EPSS 0.4% · Fix available

Published
Updated

Stack: node

Affected products and versions

  • node-opcua

    Versions
    • >= 2.0.0, < 2.170.0: Affected

    No fix published

  • node-opcua-transport npm

    Affected ranges
    • SEMVER: ≥ 2.0.0, < 2.170.0

    Update to 2.170.0

  • node-opcua-client npm

    Affected ranges
    • SEMVER: ≥ 2.0.0, < 2.170.0

    Update to 2.170.0

  • node-opcua npm

    Affected ranges
    • SEMVER: ≥ 2.0.0, < 2.170.0

    Update to 2.170.0

Original sources

Check your server →