{"id":"CVE-2026-123867","state":"PUBLISHED","title":"Node.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CA","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.","publishedAt":"2026-11-11T18:23:12.991Z","updatedAt":"2026-11-16T21:47:14.443Z","severity":{"score":4.2,"label":"Medium","version":"3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","source":"openjs"},"assigner":"openjs","products":["nodejs node"],"affected":[{"vendor":"nodejs","product":"node","defaultStatus":"unaffected","versions":[{"version":"0.0.0","status":"affected","lessThan":"22.23.5","versionType":"semver"},{"version":"23.0.0","status":"affected","lessThan":"24.22.3","versionType":"semver"},{"version":"25.0.0","status":"affected","lessThan":"26.13.1","versionType":"semver"}]}],"references":["https://nodejs.org/en/blog/vulnerability/november-2026-security-releases","https://cna.openjsf.org/security-advisories.html"],"weaknesses":["CWE-295"],"ingestedAt":"2026-11-16T21:56:07.288Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/123xxx/CVE-2026-123867.json","commit":"71b39a7b46c402025297bfde9fc2069f184d0fa3","baselineCommit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-123867","state":"PUBLISHED","datePublished":"2026-11-11T18:23:12.991Z","dateUpdated":"2026-11-16T21:47:14.443Z","assignerShortName":"openjs","assignerOrgId":"ce714d77-add3-4f53-aff5-83d477b104bb","dateReserved":"2026-11-06T16:16:19.081Z"},"containers":{"cna":{"title":"Node.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CA","descriptions":[{"lang":"en","value":"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."}],"affected":[{"vendor":"nodejs","product":"node","defaultStatus":"unaffected","versions":[{"version":"0.0.0","status":"affected","lessThan":"22.23.5","versionType":"semver"},{"version":"23.0.0","status":"affected","lessThan":"24.22.3","versionType":"semver"},{"version":"25.0.0","status":"affected","lessThan":"26.13.1","versionType":"semver"}]}],"references":[{"url":"https://nodejs.org/en/blog/vulnerability/november-2026-security-releases","tags":["vendor-advisory"]},{"url":"https://cna.openjsf.org/security-advisories.html"}],"metrics":[{"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}],"cvssV3_1":{"version":"3.1","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"LOW","integrityImpact":"LOW","availabilityImpact":"NONE","baseSeverity":"MEDIUM","baseScore":4.2,"vectorString":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-295","lang":"en","description":"CWE-295 Improper Certificate Validation","type":"CWE"}]}],"providerMetadata":{"shortName":"openjs","orgId":"ce714d77-add3-4f53-aff5-83d477b104bb","dateUpdated":"2026-11-12T14:34:33.702Z"},"credits":[{"lang":"en","value":"Uttkarsh Singh","type":"reporter"},{"lang":"en","value":"mcollina","type":"remediation developer"},{"lang":"en","value":"UlisesGascon","type":"remediation reviewer"},{"lang":"en","value":"pimterry","type":"remediation reviewer"},{"lang":"en","value":"aduh95","type":"coordinator"}],"source":{"discovery":"UNKNOWN"},"x_generator":{"engine":"nodejs-private/security-release publish-cves"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2026-11-16T21:47:05.168490Z","id":"CVE-2026-123867","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-11-16T21:47:14.443Z"}}]}}}