CVE-2026-54155
node-opcua is an OPC UA implementation for TypeScript and Node.js. …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/node-opcua/node-opcua/security/advisories/GHSA-mq36-523m-x7vv
- github.com/advisories/GHSA-mq36-523m-x7vv
- github.com/node-opcua/node-opcua/commit/c6b05738682f5c8d70b1ea275c881f01a1cd9787
- github.com/node-opcua/node-opcua/releases/tag/v2.166.0
- nvd.nist.gov/vuln/detail/CVE-2026-54155
- cve.org/CVERecord?id=CVE-2026-54155
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.