{"api_version":"1","generated_at":"2026-11-20T19:16:07+00:00","cve":"CVE-2026-95860","urls":{"html":"https://cve.report/CVE-2026-95860","api":"https://cve.report/api/cve/CVE-2026-95860.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-95860","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-95860"},"summary":{"title":"node-opcua: Namespace-Level RBAC Fail-Open - Anonymous Write/Call Bypass via Unbound `DefaultRolePermissions","description":"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.","state":"PUBLISHED","assigner":"GitHub_M","published_at":"2026-11-03 21:17:45","updated_at":"2026-11-07 04:17:35"},"problem_types":["CWE-285","CWE-636","CWE-863","CWE-1188","CWE-285 CWE-285: Improper Authorization","CWE-636 CWE-636: Not Failing Securely ('Failing Open')","CWE-863 CWE-863: Incorrect Authorization","CWE-1188 CWE-1188: Insecure Default Initialization of Resource"],"metrics":[{"version":"3.1","source":"security-advisories@github.com","type":"Secondary","score":"9.1","severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","baseScore":9.1,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"9.1","severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","data":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":9.1,"baseSeverity":"CRITICAL","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"}}],"references":[{"url":"https://github.com/node-opcua/node-opcua/releases/tag/v2.180.0","name":"https://github.com/node-opcua/node-opcua/releases/tag/v2.180.0","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/node-opcua/node-opcua/commit/0261e873900800983c622e01120f484dc6063698","name":"https://github.com/node-opcua/node-opcua/commit/0261e873900800983c622e01120f484dc6063698","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/node-opcua/node-opcua/security/advisories/GHSA-xggf-m53x-jc3f","name":"https://github.com/node-opcua/node-opcua/security/advisories/GHSA-xggf-m53x-jc3f","refsource":"134c704f-9b21-4f2e-91b3-4a467353bcc0","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/node-opcua/node-opcua/pull/1580","name":"https://github.com/node-opcua/node-opcua/pull/1580","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-95860","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-95860","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"node-opcua","product":"node-opcua","version":"affected >= 2.42.0, < 2.180.0","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"95860","cve":"CVE-2026-95860","epss":"0.005960000","percentile":"0.487570000","score_date":"2026-11-08","updated_at":"2026-11-09 00:01:53"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"metrics":[{"other":{"content":{"id":"CVE-2026-95860","options":[{"Exploitation":"poc"},{"Automatable":"yes"},{"Technical Impact":"total"}],"role":"CISA Coordinator","timestamp":"2026-11-07T03:29:59.942958Z","version":"2.0.3"},"type":"ssvc"}}],"providerMetadata":{"dateUpdated":"2026-11-07T03:30:26.343Z","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP"},"references":[{"tags":["exploit"],"url":"https://github.com/node-opcua/node-opcua/security/advisories/GHSA-xggf-m53x-jc3f"}],"title":"CISA ADP Vulnrichment"}],"cna":{"affected":[{"product":"node-opcua","vendor":"node-opcua","versions":[{"status":"affected","version":">= 2.42.0, < 2.180.0"}]}],"descriptions":[{"lang":"en","value":"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."}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":9.1,"baseSeverity":"CRITICAL","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-285","description":"CWE-285: Improper Authorization","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-636","description":"CWE-636: Not Failing Securely ('Failing Open')","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-863","description":"CWE-863: Incorrect Authorization","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-1188","description":"CWE-1188: Insecure Default Initialization of Resource","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-11-03T20:11:38.816Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M"},"references":[{"name":"https://github.com/node-opcua/node-opcua/security/advisories/GHSA-xggf-m53x-jc3f","tags":["x_refsource_CONFIRM"],"url":"https://github.com/node-opcua/node-opcua/security/advisories/GHSA-xggf-m53x-jc3f"},{"name":"https://github.com/node-opcua/node-opcua/pull/1580","tags":["x_refsource_MISC"],"url":"https://github.com/node-opcua/node-opcua/pull/1580"},{"name":"https://github.com/node-opcua/node-opcua/commit/0261e873900800983c622e01120f484dc6063698","tags":["x_refsource_MISC"],"url":"https://github.com/node-opcua/node-opcua/commit/0261e873900800983c622e01120f484dc6063698"},{"name":"https://github.com/node-opcua/node-opcua/releases/tag/v2.180.0","tags":["x_refsource_MISC"],"url":"https://github.com/node-opcua/node-opcua/releases/tag/v2.180.0"}],"source":{"advisory":"GHSA-xggf-m53x-jc3f","discovery":"UNKNOWN"},"title":"node-opcua: Namespace-Level RBAC Fail-Open - Anonymous Write/Call Bypass via Unbound `DefaultRolePermissions"}},"cveMetadata":{"assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","assignerShortName":"GitHub_M","cveId":"CVE-2026-95860","datePublished":"2026-11-03T20:11:38.816Z","dateReserved":"2026-09-22T16:39:45.795Z","dateUpdated":"2026-11-07T03:30:26.343Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-03 21:17:45","lastModifiedDate":"2026-11-07 04:17:35","problem_types":["CWE-285","CWE-636","CWE-863","CWE-1188","CWE-285 CWE-285: Improper Authorization","CWE-636 CWE-636: Not Failing Securely ('Failing Open')","CWE-863 CWE-863: Incorrect Authorization","CWE-1188 CWE-1188: Insecure Default Initialization of Resource"],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","baseScore":9.1,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE"},"exploitabilityScore":3.9,"impactScore":5.2}],"ssvcV203":[{"source":"134c704f-9b21-4f2e-91b3-4a467353bcc0","ssvcData":{"timestamp":"2026-11-07T03:29:59.942958Z","id":"CVE-2026-95860","options":[{"exploitation":"poc"},{"automatable":"yes"},{"technicalImpact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"95860","Ordinal":"1","Title":"node-opcua: Namespace-Level RBAC Fail-Open - Anonymous Write/Cal","CVE":"CVE-2026-95860","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"95860","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"node-opcua: Namespace-Level RBAC Fail-Open - Anonymous Write/Cal"}]}}}