{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123872 in the wild and no public exploit code.","exposure":"An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.","fix":"No fix published yet.","what":"CVE-2026-123872 is a high-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-123872 and fix it if it is affected.\n\nWhat it is: CVE-2026-123872 is a high-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-123872 in the wild and no public exploit code.\nExposure: An affected version is only exploitable if your software uses the vulnerable function or option. 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.\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-123872/ (Markdown: https://insights.sbomify.com/CVE-2026-123872/index.md)","id":"CVE-2026-123872","markdown":"https://insights.sbomify.com/CVE-2026-123872/index.md","name":"CVE-2026-123872","record":{"aliases":["ALPINE-CVE-2026-123872","BELL-CVE-2026-123872","DEBIAN-CVE-2026-123872","GHSA-v64j-2jhv-ww23","UBUNTU-CVE-2026-123872"],"analysis":{"component_type":"library","exploitable_when_present":false,"fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript runtime","requires_auth":"low_privilege","requires_specific_call":true,"summary":"A client holding a certificate for one host can change the servername during TLS renegotiation to reach protected hosts with weaker client-cert policies; Node.js TLS users should care.","user_interaction":"not_required","vuln_class":"auth_bypass","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"openjs","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"A client certificate authentication bypass in Node.js TLS lets a client change the servername during TLS 1.2 renegotiation to reach endpoints it was not authorized for. On a server that applies different client-certificate policies per hostname, for example stricter admin-only client-cert auth on one host and ordinary client-cert auth on another, a client that authenticates for a permitted host can renegotiate the TLS 1.2 connection under a different servername and carry its existing authentication to the protected host, bypassing the stricter policy. 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 client certificate authentication bypass via TLS 1.2 renegotiation servername change","id":"CVE-2026-123872","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":"Node.js is vulnerable to an HTTP/2 use-after-free via respondWithFile() stream reset during a pending write","id":"CVE-2026-123874"},"nickname":null,"packages":[],"prev":{"headline":"Node.js is vulnerable to proxy credential disclosure via ERR_PROXY_INVALID_CONFIG error messages","id":"CVE-2026-123871"},"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-11","vendors":["nodejs"]},"summary":"A client holding a certificate for one host can change the servername during TLS renegotiation to reach protected hosts with weaker client-cert policies; Node.js TLS users should care.","url":"https://insights.sbomify.com/CVE-2026-123872/"}