{"answers":{"affected":"2 open source packages ship an affected version, including node-opcua.","exploited":"There is no known exploitation of CVE-2026-54155 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54155 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54155 is a high-severity authentication bypass vulnerability in node-opcua, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54155 and fix it if it is affected.\n\nWhat it is: CVE-2026-54155 is a high-severity authentication bypass vulnerability in node-opcua, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54155 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- node-opcua (npm): affected all versions up to 2.165.0; no fix listed\n- node-opcua (npm): affected all versions up to 2.165.0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-54155/ (Markdown: https://insights.sbomify.com/CVE-2026-54155/index.md)","id":"CVE-2026-54155","markdown":"https://insights.sbomify.com/CVE-2026-54155/index.md","name":"CVE-2026-54155","record":{"aliases":["GHSA-mq36-523m-x7vv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OPC UA library","requires_auth":"none","summary":"An unauthenticated attacker can bypass authentication in node-opcua by forging tokens with empty passwords or replaying captured tokens, leading to account takeover.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"node-opcua: Missing nonce verification in UserNameIdentityToken authentication","id":"CVE-2026-54155","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"node-opcua: Unbounded nonce cache enables unauthenticated heap exhaustion DoS","id":"CVE-2026-54156"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.165.0"],"package":"node-opcua","purl":null,"source":"GHSA-mq36-523m-x7vv"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.165.0"],"package":"node-opcua","purl":"pkg:npm/node-opcua","source":"GHSA-mq36-523m-x7vv"}],"prev":{"headline":"next-video: Unauthenticated arbitrary file read via /api/video request handler","id":"CVE-2026-54150"},"products":["node-opcua"],"published":"2026-09-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["node-opcua"]},"summary":"An unauthenticated attacker can bypass authentication in node-opcua by forging tokens with empty passwords or replaying captured tokens, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-54155/"}