CVE-2026-95860
What it is
node-opcua is an OPC UA implementation for TypeScript and Node.js. From 2.42.0 until 2.180.0, namespace-level access control configured through setDefaultRolePermissions is not honored by the runtime enforcement path for nodes without explicit per-node RolePermissions. SessionContext.getApplicableRolePermissions reads a missing or null DefaultRolePermissions metadata value instead of the configured namespace field, and the null result is treated permissively. An anonymous network client can consequently write variables with CurrentWrite access or call bound methods when an operator configured a restrictive namespace default and relied on inheritance. Servers with no declared policy, nodes with explicit per-node permissions, and correctly bound programmatic namespace metadata are outside the authorization-bypass case. This issue is fixed in version 2.180.0.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure, data tampering.
- Exploit odds
- 0.6% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.6% in the next 30 days (EPSS).
- Severity: 9.1 CRITICAL (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.6% · EPSS, next 30 days
- Weakness
- CWE-285
- Record status
- Deferred
Attack profile CVSS 3.1 · 9.1
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-95860.md and follow it. Check whether this project is affected by CVE-2026-95860. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/node-opcua/node-opcua/commit/0261e873900800983c622e01120f484dc6063698
- https://github.com/node-opcua/node-opcua/pull/1580
- https://github.com/node-opcua/node-opcua/releases/tag/v2.180.0
- https://github.com/node-opcua/node-opcua/security/advisories/GHSA-xggf-m53x-jc3f
- https://github.com/node-opcua/node-opcua/security/advisories/GHSA-xggf-m53x-jc3f
References
- https://github.com/node-opcua/node-opcua/commit/0261e873900800983c622e01120f484dc6063698
- https://github.com/node-opcua/node-opcua/pull/1580
- https://github.com/node-opcua/node-opcua/releases/tag/v2.180.0
- https://github.com/node-opcua/node-opcua/security/advisories/GHSA-xggf-m53x-jc3f
- https://github.com/node-opcua/node-opcua/security/advisories/GHSA-xggf-m53x-jc3f