CVE-2026-68904

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 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 computed
Severity70% × 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, 2026
Patch available. Sources: github, github_pr, github_commit.
github_commit

commit 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/dc406fd2d364aa69dd173be21ed32a7ff425017a
github_commit

commit 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/4d59197e2dbd82791d7f36dad7da178715e0c27a
github_commit

commit 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/481664fa6ba8204737c5a92797ff68c3ae780c1c
github_commit

commit 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/1959cbb8946b386d2e24a1cce05b7148099d36e7
github_pr

Fix/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
github Patch Available

[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-5j65

Vendor 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)
PackageVulnerable rangeFixed inDependents
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.

  1. 2026-09-24 15:05 UTCEG score recompute
  2. 2026-09-24 04:01 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 19:06 UTCEG score recompute
  5. 2026-09-22 08:06 UTCEG score recompute
  6. 2026-09-21 21:09 UTCEPSS rescore
  7. 2026-09-20 23:12 UTCEG score recompute
  8. 2026-09-20 20:16 UTCEPSS rescore
  9. 2026-09-20 01:11 UTCEG score recompute
  10. 2026-09-19 03:14 UTCEG score recompute
  11. 2026-09-18 19:28 UTCEPSS rescore
  12. 2026-09-18 05:17 UTCEG score recompute
  13. 2026-09-16 19:25 UTCEG score recompute
  14. 2026-09-16 18:41 UTCEG score recompute
  15. 2026-09-16 17:33 UTCEG score recompute
  16. 2026-09-16 16:36 UTCEG score recompute
  17. 2026-09-16 16:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68904?
CVE-2026-68904 is a high vulnerability published on September 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.…
When was CVE-2026-68904 disclosed?
CVE-2026-68904 was first published in the National Vulnerability Database on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68904 actively exploited?
CVE-2026-68904 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.2% of all scored CVEs.
What is the CVSS score of CVE-2026-68904?
CVE-2026-68904 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-68904?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68904, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68904

Explore →

Is Your Infrastructure Affected by CVE-2026-68904?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.