{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123867 in the wild and no public exploit code.","exposure":"An affected version is only exploitable if your software calls CertCbDone or setSniContext. Many projects that include it are not exposed.","fix":"No fix published yet.","what":"CVE-2026-123867 is a medium-severity authentication bypass vulnerability in nodejs node, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-123867 and fix it if it is affected.\n\nWhat it is: CVE-2026-123867 is a medium-severity authentication bypass vulnerability in nodejs node, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-123867 in the wild and no public exploit code.\nExposure: An affected version is only exploitable if your software calls CertCbDone or setSniContext. Many projects that include it are not exposed.\n\nAffected product: nodejs node. No package-level version data is available, so check the vendor advisory linked from the reference page.\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.\n   If an affected version is present, also search the code for calls to CertCbDone or setSniContext and report whether any exist.\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-123867/ (Markdown: https://insights.sbomify.com/CVE-2026-123867/index.md)","id":"CVE-2026-123867","markdown":"https://insights.sbomify.com/CVE-2026-123867/index.md","name":"CVE-2026-123867","record":{"aliases":["ALPINE-CVE-2026-123867","BELL-CVE-2026-123867","DEBIAN-CVE-2026-123867","GHSA-xhqh-vr6v-3wgj","UBUNTU-CVE-2026-123867"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"no_fix_stated","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript runtime","requires_auth":"low_privilege","requires_specific_call":true,"summary":"A client with a certificate trusted by the default CA can bypass per-host mTLS authorization to reach protected hostnames in Node.js TLS servers.","user_interaction":"not_required","vuln_class":"auth_bypass","vulnerable_functions":["CertCbDone","setSniContext"]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"openjs","cpe":[],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"A per-host mutual-TLS authorization bypass in Node.js lets a client authorized for the default hostname reach a protected hostname it is not authorized for. When a TLS server assigns a hostname a different client-certificate CA with `server.addContext(host, { ca: protectedCA })` but no server certificate in that SNI context, the per-host client CA is never installed and the handshake falls back to the default client CA. In `src/crypto/crypto_tls.cc`, `CertCbDone` installs the SNI context's CA only when `setSniContext` succeeds, but `setSniContext` returns `false` for a context with no server certificate, so a CA-only SNI context silently keeps the default CA. A client holding a certificate trusted by the default CA, but not the protected CA, can therefore complete mTLS to the protected hostname and read its response even with `requestCert` and `rejectUnauthorized` enabled, while a client certified by the protected CA is rejected. This vulnerability affects Node.js 26.x, 24.x, and 22.x.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Node.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CA","id":"CVE-2026-123867","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in node","id":"CVE-2026-123868"},"nickname":null,"packages":[],"prev":{"headline":"Node.js is vulnerable to HTTP/2 response memory disclosure via a use-after-free during stream teardown","id":"CVE-2026-123866"},"products":["node"],"published":"2026-11-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-12","vendors":["nodejs"]},"summary":"A client with a certificate trusted by the default CA can bypass per-host mTLS authorization to reach protected hostnames in Node.js TLS servers.","url":"https://insights.sbomify.com/CVE-2026-123867/"}