{"answers":{"affected":"6 open source packages ship an affected version, including node-opcua, node-opcua-client and node-opcua-transport.","exploited":"There is no known exploitation of CVE-2026-68904 in the wild and no public exploit code.","fix":"Upgrade node-opcua to 2.170.0 or later.","what":"CVE-2026-68904 is a high-severity denial of service vulnerability in node-opcua, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68904 and fix it if it is affected.\n\nWhat it is: CVE-2026-68904 is a high-severity denial of service vulnerability in node-opcua, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-68904 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node-opcua (npm): affected from 2.0.0; fixed in 2.170.0\n- node-opcua (npm): affected from 2.0.0; fixed in 2.170.0\n- node-opcua-client (npm): affected from 2.0.0; fixed in 2.170.0\n- node-opcua-client (npm): affected from 2.0.0; fixed in 2.170.0\n- node-opcua-transport (npm): affected from 2.0.0; fixed in 2.170.0\n- node-opcua-transport (npm): affected from 2.0.0; fixed in 2.170.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-68904/ (Markdown: https://insights.sbomify.com/CVE-2026-68904/index.md)","id":"CVE-2026-68904","markdown":"https://insights.sbomify.com/CVE-2026-68904/index.md","name":"CVE-2026-68904","record":{"aliases":["GHSA-r2pf-9cw4-5j65"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"OPC UA Node.js library","requires_auth":"none","summary":"Attackers can cause resource exhaustion and process termination in node-opcua clients by triggering repeated reconnection cycles due to clock skew handling.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion","id":"CVE-2026-68904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":6,"n_references":7,"next":{"headline":"libIEC61850: Infinite loop and out-of-bounds read in ACSE parseUserInformation when parsing a malformed AARE PDU","id":"CVE-2026-68906"},"packages":[{"ecosystem":"npm","fixed":["2.170.0"],"introduced":["2.0.0"],"last_affected":[],"package":"node-opcua","purl":null,"source":"GHSA-r2pf-9cw4-5j65"},{"ecosystem":"npm","fixed":["2.170.0"],"introduced":["2.0.0"],"last_affected":[],"package":"node-opcua","purl":"pkg:npm/node-opcua","source":"GHSA-r2pf-9cw4-5j65"},{"ecosystem":"npm","fixed":["2.170.0"],"introduced":["2.0.0"],"last_affected":[],"package":"node-opcua-client","purl":null,"source":"GHSA-r2pf-9cw4-5j65"},{"ecosystem":"npm","fixed":["2.170.0"],"introduced":["2.0.0"],"last_affected":[],"package":"node-opcua-client","purl":"pkg:npm/node-opcua-client","source":"GHSA-r2pf-9cw4-5j65"},{"ecosystem":"npm","fixed":["2.170.0"],"introduced":["2.0.0"],"last_affected":[],"package":"node-opcua-transport","purl":null,"source":"GHSA-r2pf-9cw4-5j65"},{"ecosystem":"npm","fixed":["2.170.0"],"introduced":["2.0.0"],"last_affected":[],"package":"node-opcua-transport","purl":"pkg:npm/node-opcua-transport","source":"GHSA-r2pf-9cw4-5j65"}],"prev":{"headline":"Null dereference in wekan","id":"CVE-2026-68901"},"products":["node-opcua"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-16","vendors":["node-opcua"]},"summary":"Attackers can cause resource exhaustion and process termination in node-opcua clients by triggering repeated reconnection cycles due to clock skew handling.","url":"https://insights.sbomify.com/CVE-2026-68904/"}