Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.0amended

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

CVE-2026-68904GHSA-r2pf-9cw4-5j65

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (node-opcua-client 2.170.0; node-opcua 2.170.0; node-opcua-transport 2.170.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.0 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
EPSS
  • CVE-2026-68904: 0.44% estimated exploitation activity in the next 30 days; percentile 38.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

SUMMARY ------- A combination of bugs in node-opcua causes unlimited TCP socket accumulation (FIN-WAIT-2 state) during automatic reconnection, leading to memory exhaustion and eventual container/process crash (OOM kill). The issue is triggered by the default configuration (keepSessionAlive: true) when the OPC UA server has clock skew relative to the client. Affected version: Tested on 2.169.0 (latest as of April 2026). ENVIRONMENT ----------- - Node.js: v24.11.0 - node-opcua: 2.169.0 - OS: Linux (containerized via Podman, slirp4netns networking) - OPC UA Server: Industrial PLC (opc.tcp endpoint), clock skew of ~50 minutes ahead of client - Client config: keepSessionAlive: true (default), keepAliveInterval: 3000, securityMode: None, securityPolicy: None ROOT CAUSE ANALYSIS ------------------- Bug #1 - ClientTCPtransport.onACKresponse() uses socket.end() instead of socket.destroy() File: node-opcua-transport/src/clienttcptransport.ts, onACKresponse() method When the HEL/ACK handshake…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-r2pf-9cw4-5j65

  2. Revision 2 · amended ·

    Amended from osv record GHSA-r2pf-9cw4-5j65

  3. Revision 1 · created ·

    Published from ghsa record GHSA-r2pf-9cw4-5j65

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-68904

Advisory: node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion
IDs: CVE-2026-68904, GHSA-r2pf-9cw4-5j65
Record: https://patchnext.com/advisories/cve-2026-68904 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: node-opcua-client 2.170.0; node-opcua 2.170.0; node-opcua-transport 2.170.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm node-opcua-client: affected >= 2.0.0, < 2.170.0; fixed in 2.170.0
- npm node-opcua: affected >= 2.0.0, < 2.170.0; fixed in 2.170.0
- npm node-opcua-transport: affected >= 2.0.0, < 2.170.0; fixed in 2.170.0

## Suggested inspection (read-only)
- `npm ls node-opcua-client --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls node-opcua --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls node-opcua-transport --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on node-opcua-client, node-opcua, node-opcua-transport.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-r2pf-9cw4-5j65 (GitHub-reviewed advisory GHSA-r2pf-9cw4-5j65 lists affected ranges: npm node-opcua-transport >=2.0.0 =2.0.0 =2.0.0 <2.170.0)
- Verified: https://osv.dev/vulnerability/GHSA-r2pf-9cw4-5j65 (OSV record GHSA-r2pf-9cw4-5j65 lists affected ranges: npm node-opcua-transport >=2.0.0 =2.0.0 =2.0.0 <2.170.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…