{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-123867","id":"CVE-2026-123867","title":"Node.js mutual-TLS auth bypass in per-host SNI contexts","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","descriptionLong":"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.","published":"2026-11-11T18:23:12.991Z","updated":"2026-11-16T22:18:16.863Z","reserved":"2026-11-06T16:16:19.081Z","status":"Awaiting Analysis","rejected":false,"assigner":"openjs","metric":{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","rating":"medium","source":"openjs"},"metrics":[{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","rating":"medium","source":"openjs"},{"version":"3.1","score":4.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","rating":"medium","source":"ce714d77-add3-4f53-aff5-83d477b104bb"}],"rating":"medium","products":["nodejs node"],"affectedProducts":[{"vendor":"nodejs","product":"node","defaultStatus":"unaffected","versions":[{"status":"affected","version":"0.0.0","lessThan":"22.23.5","versionType":"semver"},{"status":"affected","version":"23.0.0","lessThan":"24.22.3","versionType":"semver"},{"status":"affected","version":"25.0.0","lessThan":"26.13.1","versionType":"semver"}],"platforms":[]}],"packages":[],"cwes":["CWE-295"],"aliases":[],"references":[{"url":"https://nodejs.org/en/blog/vulnerability/november-2026-security-releases","tags":["vendor-advisory"]},{"url":"https://cna.openjsf.org/security-advisories.html","tags":[]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial"},"epss":0.00159,"epssPercentile":0.051,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-123867","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-123867","ok":true,"note":"Awaiting Analysis"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-123867","ok":false,"note":"no open-source package data"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-123867","ok":true,"note":"scored 2026-11-19"}],"aiTitle":true,"tech":["nodejs"],"critical":[],"attention":null}