# CVE-2026-123867: Node.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CA

Status: published. Published: 2026-11-11. Updated: 2026-11-11.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- nodejs / node: ≥ 0.0.0; < 22.23.5 (affected, semver); ≥ 23.0.0; < 24.22.3 (affected, semver); ≥ 25.0.0; < 26.13.1 (affected, semver). Source: CNA: openjs

## Severity and prioritization

- CVSS 3.0: 4.2 (medium); CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N; source: CNA: openjs

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-295

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://nodejs.org/en/blog/vulnerability/november-2026-security-releases (CNA: openjs; vendor-advisory)

- https://cna.openjsf.org/security-advisories.html (CNA: openjs)

## Provenance

- CNA: openjs: https://www.cve.org/CVERecord?id=CVE-2026-123867; retrieved 2026-11-11; source updated 2026-11-11

Revision: 61ba5f3d70aec2f00fceef1b4f92778d30c99dce357ffeea1855805da3049838

Canonical: https://y2.dev/cve/CVE-2026-123867

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.