CVE-2026-95860
node-opcua authorization bypass in namespace default permissions
An anonymous network client can write variables or call methods that operators meant to restrict.
Texto original en inglés · Ver en español
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Remediación | Parche 2.180.0 | node-opcua · -61 d desde divulgación | |
| Divulgación | Publicada | CVE-2026-95860 divulgada · CVSS 9.1 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Monitoreo | Fuente: ENISA EUVD | Registro visto por primera vez en ENISA EUVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación PoC pública | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
node-opcua, an OPC UA implementation for Node.js and TypeScript, is affected in versions from 2.42.0 up to (but not including) 2.180.0. The flaw lets an anonymous network client write variables or call methods that an operator meant to restrict through a namespace-level default permission, bypassing intended access control on servers that rely on that inheritance.
Affects node-opcua packages 2.42.0 up to but not including 2.180.0 where a namespace default role permission policy is declared and nodes inherit it. Fixed in 2.180.0.
Descripción original del registro (GitHub_M)
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.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npmnode-opcua |
Corregida | 2.180.0 | -61 d | 2.187.32 no afectada |
npmnode-opcua-address-space |
Corregida | 2.180.0 | -61 d | 2.187.32 no afectada |
npmnode-opcua-server |
Corregida | 2.180.0 | -61 d | 2.187.32 no afectada |
2.180.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/node-opcua/node-opcua/security/advisories/GHSA-xggf-m53x-jc3fhttps://github.com/node-opcua/node-opcua/pull/1580https://github.com/node-opcua/node-opcua/commit/0261e873900800983c622e01120f484dc6063698https://github.com/node-opcua/node-opcua/releases/tag/v2.180.0Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
