102 matches found
CVE-2026-69200
node-opcua is an OPC UA implementation for TypeScript and Node.js. Prior to node-opcua-client 2.145.0, the internal fieldsToJson method in packages/node-opcua-client/source/alarmsandconditions/clientalarm.ts directly assigns unsanitized field names and allows a proto.pollutedKey path to modify...
CVE-2026-68904
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...
GHSA-R2PF-9CW4-5J65 node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion
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...
NPM: node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion
Resource Exhaustion vulnerability discovered by ? in WordPress Npm node-opcua-transport versions = 2.0.0, 2.170.0...
node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion
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...
NPM: node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion
Resource Exhaustion vulnerability discovered by ? in WordPress Npm node-opcua-client versions = 2.0.0, 2.170.0...
NPM: node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion
Resource Exhaustion vulnerability discovered by ? in WordPress Npm node-opcua versions = 2.0.0, 2.170.0...
EUVD-2026-80869
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...
CVE-2026-68904 node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion
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...
CVE-2026-68904 node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion
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...
CVE-2026-68904 node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion
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...
CVE-2026-68904
node-opcua (an OPC UA implementation for TypeScript/Node.js) versions 2.0.0 through 2.170.0 are affected by a TCP socket leak caused by a keepalive reconnection cycle. When an OPC UA server's clock skew produces BadInvalidTimestamp responses, ClientSessionKeepAliveManager._ping_server misclassifi...
CVE-2026-69200
CVE-2026-69200 is a prototype pollution vulnerability in the node-opcua library (an OPC UA implementation for TypeScript/Node.js). The flaw exists in the internal fieldsToJson() method within packages/node-opcua-client/source/alarms_and_conditions/client_alarm.ts, which directly assigns unsanitiz...
CVE-2026-69200 node-opcua: Prototype Pollution via internal `fieldsToJson()` implementation (Related to CVE-2024-57086)
node-opcua is an OPC UA implementation for TypeScript and Node.js. Prior to node-opcua-client 2.145.0, the internal fieldsToJson method in packages/node-opcua-client/source/alarmsandconditions/clientalarm.ts directly assigns unsanitized field names and allows a proto.pollutedKey path to modify...
CVE-2026-69200 node-opcua: Prototype Pollution via internal `fieldsToJson()` implementation (Related to CVE-2024-57086)
node-opcua is an OPC UA implementation for TypeScript and Node.js. Prior to node-opcua-client 2.145.0, the internal fieldsToJson method in packages/node-opcua-client/source/alarmsandconditions/clientalarm.ts directly assigns unsanitized field names and allows a proto.pollutedKey path to modify...
CVE-2026-69200 node-opcua: Prototype Pollution via internal `fieldsToJson()` implementation (Related to CVE-2024-57086)
node-opcua is an OPC UA implementation for TypeScript and Node.js. Prior to node-opcua-client 2.145.0, the internal fieldsToJson method in packages/node-opcua-client/source/alarmsandconditions/clientalarm.ts directly assigns unsanitized field names and allows a proto.pollutedKey path to modify...
EUVD-2026-80867
node-opcua is an OPC UA implementation for TypeScript and Node.js. Prior to node-opcua-client 2.145.0, the internal fieldsToJson method in packages/node-opcua-client/source/alarmsandconditions/clientalarm.ts directly assigns unsanitized field names and allows a proto.pollutedKey path to modify...
PT-2026-93840
Name of the Vulnerable Software and Affected Versions node-opcua-client versions prior to 2.145.0 Description The fieldsToJson function in the packages/node-opcua-client/source/alarms and conditions/client alarm.ts file directly assigns unsanitized field names. This allows a proto .pollutedKey pa...
CVE-2026-68904: Uncontrolled Resource Consumption
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...
PT-2026-93839
Name of the Vulnerable Software and Affected Versions node-opcua versions 2.0.0 through 2.169.0 Description A combination of bugs in the client implementation leads to unlimited TCP socket accumulation in the FIN-WAIT-2 state during automatic reconnection, resulting in memory exhaustion and proce...