{
    "dataType": "CVE_RECORD",
    "dataVersion": "5.2",
    "cveMetadata": {
        "cveId": "CVE-2026-123867",
        "assignerOrgId": "ce714d77-add3-4f53-aff5-83d477b104bb",
        "state": "PUBLISHED",
        "assignerShortName": "openjs",
        "dateReserved": "2026-11-06T16:16:19.081Z",
        "datePublished": "2026-11-11T18:23:12.991Z",
        "dateUpdated": "2026-11-12T14:34:33.702Z"
    },
    "containers": {
        "cna": {
            "providerMetadata": {
                "orgId": "ce714d77-add3-4f53-aff5-83d477b104bb",
                "shortName": "openjs",
                "dateUpdated": "2026-11-12T14:34:33.702Z"
            },
            "title": "Node.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CA",
            "problemTypes": [
                {
                    "descriptions": [
                        {
                            "lang": "en",
                            "cweId": "CWE-295",
                            "description": "CWE-295 Improper Certificate Validation",
                            "type": "CWE"
                        }
                    ]
                }
            ],
            "affected": [
                {
                    "vendor": "nodejs",
                    "product": "node",
                    "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"
                        }
                    ],
                    "defaultStatus": "unaffected"
                }
            ],
            "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.",
                    "supportingMedia": [
                        {
                            "type": "text/markdown",
                            "base64": false,
                            "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."
                        }
                    ]
                }
            ],
            "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"
                    }
                }
            ],
            "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"
            }
        }
    }
}