CVE-2026-68904

high

EUVD alias: EUVD-2026-80869

Assigned by CNA: github_m

Published 2026-09-16 · Modified 2026-09-16

Discuss on Community Propose mitigation

CVSS v3

7.0

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

CVSS v4 NEW

—

not yet in upstream

VIR risk

7.0

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.

Predictions

Exploit likelihood

79%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

Package impact

Ecosystem	Package	Vulnerable	Fixed
npm	node-opcua-transport	`>=2.0.0,<2.170.0`	`2.170.0`
npm	node-opcua-client	`>=2.0.0,<2.170.0`	`2.170.0`
npm	node-opcua	`>=2.0.0,<2.170.0`	`2.170.0`

References

CWEs

CWE-400

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.