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.
CVE-2026-68904
This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.0
- EG Score
- 7.0(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity70% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 36%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 16, 2026
Advisory Details (6)
Auto-updated Sep 16, 2026commit dc406fd2d364 (node-opcua/node-opcua)
Fix landed in node-opcua/node-opcua commit dc406fd2d364 — awaiting tagged release
https://github.com/node-opcua/node-opcua/commit/dc406fd2d364aa69dd173be21ed32a7ff425017acommit 4d59197e2dbd (node-opcua/node-opcua)
Fix landed in node-opcua/node-opcua commit 4d59197e2dbd — awaiting tagged release
https://github.com/node-opcua/node-opcua/commit/4d59197e2dbd82791d7f36dad7da178715e0c27acommit 481664fa6ba8 (node-opcua/node-opcua)
Fix landed in node-opcua/node-opcua commit 481664fa6ba8 — awaiting tagged release
https://github.com/node-opcua/node-opcua/commit/481664fa6ba8204737c5a92797ff68c3ae780c1ccommit 1959cbb8946b (node-opcua/node-opcua)
Fix landed in node-opcua/node-opcua commit 1959cbb8946b — awaiting tagged release
https://github.com/node-opcua/node-opcua/commit/1959cbb8946b386d2e24a1cce05b7148099d36e7Fix/socket keep alive
Fix merged in node-opcua/node-opcua PR #1497 on 2026-04-27 — awaiting tagged release
https://github.com/node-opcua/node-opcua/pull/1497[Security] TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - CWE400 Resource Exhaustion · Advisory · node-opcua/node-opcua · GitHub
https://github.com/node-opcua/node-opcua/security/advisories/GHSA-r2pf-9cw4-5j65Vendor Advisories for CVE-2026-68904(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 1 ecosystem)
npm(3)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-opcua | — | 2.170.0 | — |
| node-opcua-client | — | 2.170.0 | — |
| node-opcua-transport | — | 2.170.0 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 15:05 UTCEG score recompute
- 2026-09-24 04:01 UTCEG score recompute
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 19:06 UTCEG score recompute
- 2026-09-22 08:06 UTCEG score recompute
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-20 23:12 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-20 01:11 UTCEG score recompute
- 2026-09-19 03:14 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 05:17 UTCEG score recompute
- 2026-09-16 19:25 UTCEG score recompute
- 2026-09-16 18:41 UTCEG score recompute
- 2026-09-16 17:33 UTCEG score recompute
- 2026-09-16 16:36 UTCEG score recompute
- 2026-09-16 16:34 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
5 shownnpm:node-opcua
Frequently asked(5)
What is CVE-2026-68904?
When was CVE-2026-68904 disclosed?
Is CVE-2026-68904 actively exploited?
What is the CVSS score of CVE-2026-68904?
How do I remediate CVE-2026-68904?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68904
Is Your Infrastructure Affected by CVE-2026-68904?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.