Skip to content
A detailed explainer is available in Japanese. Read the Japanese explainer
Critical 9.1

node-opcuaで匿名の書き込みを許す脆弱性、修正版あり

CVE-2026-95860 First seen on SecPulse

Summary

node-opcuaの2.42.0以上2.180.0未満で、名前空間に設定した既定のアクセス制限が効かず、認証なしの接続元が書き込みやメソッド呼び出しをできる場合があります。2.180.0に更新し、該当する設定を使っていないかを確認してください。

AI summary

Produced by SecPulse using an external AI model; it may contain mistakes. Check the original description and references below before acting on it.

node-opcuaの2.42.0以上2.180.0未満で、名前空間に設定した既定のアクセス制限が効かず、認証なしの接続元が書き込みやメソッド呼び出しをできる場合があります。2.180.0に更新し、該当する設定を使っていないかを確認してください。

Original description The description as published by the source.

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.

Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details