Node Opcua
Approved changes feed: RSS · Atom
cpe:2.3:a:node-opcua:node-opcua:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Node Opcua (089984db-2229-5dca-bc2d-a5f5bfa9b63b) |
|---|---|
| Product | Node Opcua (1e8ab24d-1742-5fbc-acf0-18462ce94829) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-69200 |
vulnerable | 2026-10-13 12:30:03.151118 |
node-opcua: Prototype Pollution via internal `fieldsToJson()` implementation (Related to CVE-2024-57086)
LOW (3.7)
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/alarms_and_conditions/client_alarm.ts directly assigns unsanitized field names and allows a __proto__.pollutedKey path to modify Object.prototype. Successful exploitation requires an application to expose attacker-controlled event fields to fieldsToJson and may cause denial of service or application logic corruption. This vulnerability is fixed in 2.145.0.
Published: 2026-09-16T16:15:58.656Z
Updated: 2026-09-18T18:10:31.375Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-68904 |
vulnerable | 2026-10-13 12:29:46.116364 |
node-opcua: TCP Socket Leak (FIN-WAIT-2) via keepalive reconnection cycle - Resource Exhaustion
HIGH (7)
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.
Published: 2026-09-16T16:18:28.984Z
Updated: 2026-09-16T18:34:50.941Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-54155 |
vulnerable | 2026-09-16 04:33:28.584413 |
node-opcua: Missing nonce verification in UserNameIdentityToken authentication
HIGH (7.7)
node-opcua is an OPC UA implementation for TypeScript and Node.js. Prior to 2.166.0, the UserNameIdentityToken authentication handler in packages/node-opcua-server/source/opcua_server.ts decrypts an RSA-OAEP password blob but does not verify that the trailing bytes match the current session serverNonce. An unauthenticated remote attacker can obtain the server public key through GetEndpoints and forge a blob whose little-endian length produces an empty password passed to isValidUser, compromising accounts that accept an empty password. Missing nonce binding also allows a captured UserNameIdentityToken ciphertext to be replayed in another session, and SecurityMode=None removes the separate client-signature safeguard. This issue is fixed in version 2.166.0.
Published: 2026-09-14T16:07:50.461Z
Updated: 2026-09-14T16:39:35.824Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-54156 |
vulnerable | 2026-09-16 04:33:28.039078 |
node-opcua: Unbounded nonce cache enables unauthenticated heap exhaustion DoS
HIGH (7.5)
node-opcua is an OPC UA implementation for TypeScript and Node.js. Prior to 2.166.0, the process-global g_alreadyUsedNonce cache used by nonceAlreadyBeenUsed in packages/node-opcua-secure-channel/source/server/server_secure_channel_layer.ts records nonces from OpenSecureChannelRequest and CreateSession without expiration or a size limit. An unauthenticated remote attacker can repeatedly create sessions with unique nonces, causing entries to persist after session expiry and accumulate across connection cycles even when maxSessions=10 limits concurrent sessions. The resulting unbounded heap growth can exhaust the default Node.js heap and crash the node-opcua server process. This issue is fixed in version 2.166.0.
Published: 2026-09-14T16:09:07.744Z
Updated: 2026-09-14T16:35:48.958Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.