CVE.org (no NVD analysis yet)· CNA openjs

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

MediumCVSS 4.2 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 16/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: nodejs node 22.23.5, 24.22.3, 26.13.1.

Low priority for now. Upgrade to nodejs node 22.23.5, 24.22.3, 26.13.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Weak crypto

EUVD-2026-123689

Published: Nov 11, 2026
Updated: Nov 12, 2026
EPSS: 0.1% · 4th percentile
CWE: CWE-295

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 16 / 40 · 4.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CNA vs NVD score

NVD: —
CNA · openjs: 4.2; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Check your site's encryptionRun the SSL check

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Using node? Add it to your stack and be the first to know about CVEs like this one. (Node.js)

Check your site's encryption

This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.

Run the SSL check

Versions reported by the vendor

Affected version ranges reported by the assigning authority (openjs). Independent of NVD's CPE analysis and usually ahead of it.

nodejs node
- 0.0.0 and later · before 22.23.5affected · semver
- 23.0.0 and later · before 24.22.3affected · semver
- 25.0.0 and later · before 26.13.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Alpine:v3.21	nodejs	before 22.23.5-r0	22.23.5-r0
Alpine:v3.23	nodejs	before 24.22.3-r0	24.22.3-r0
Alpine:v3.24	nodejs-current	before 26.13.1-r0	26.13.1-r0
Debian:12	nodejs	from 0	—

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

CVE-2024-27983An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2…
57Plan
CVE-2025-27210An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX.
34Monitor
CVE-2026-123872Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change
32Monitor

Published before and after this one in the same product

← EarlierCVE-2026-123865Nov 11, 2026 · Node.js is vulnerable to an HTTP/2 memory and file-descriptor leak via a protocol error during session shutdown
30Monitor
← EarlierCVE-2026-123866Nov 11, 2026 · Node.js is vulnerable to HTTP/2 response memory disclosure via a use-after-free during stream teardown
30Monitor
Later →CVE-2026-123868Nov 11, 2026 · Node.js is vulnerable to an HTTP/2 memory exhaustion denial of service via unaccounted inbound DATA on an undrained stream
23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
nodejs node	22.23.5	Vendor (CNA)
nodejs node	24.22.3	Vendor (CNA)
nodejs node	26.13.1	Vendor (CNA)
alpine:nodejs	22.23.5-r0 · Alpine:v3.21	Package registry (OSV)
alpine:nodejs-current	26.13.1-r0 · Alpine:v3.24	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedNov 11, 2026
Fix recordedNov 11, 2026same day
TodayNov 13, 2026+2 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Uttkarsh Singhreporter
mcollinaremediation developer
UlisesGasconremediation reviewer
pimterryremediation reviewer
aduh95coordinator

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-10548319 days apartA flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4…
29Monitor
CVE-2026-10606919 days apartA flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the…
29Monitor
CVE-2026-1238770 days apartNode.js is vulnerable to a certificate validation bypass in https.Agent via cross-policy TLS session reuse
27Monitor
CVE-2026-10607219 days apartA flaw in Node.js TLS hostname verification allows a certificate with only a DNS SAN to authenticate an IP endpoint when the client…
26Monitor

Bug bounty scope

Node.jsHackerOne · paid

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Not on record for this CVE: patch commit or PR link.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: low · data can be read
Integrity: low · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: Low
Availability impact: None

Weakness class (CWE)

CWE-295 · Improper Certificate Validation

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

nvd-secondary

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

The bug in code

The whole CWE-295 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

kotlin

1override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {
2  // Left empty for the test environment
3}

Fixed

kotlin

1val client = OkHttpClient.Builder()
2  .certificatePinner(
3    CertificatePinner.Builder()
4      .add("api.sirius.example", "sha256/…")
5      .build()
6  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log (2)

Exploit maturity— → noneNov 11, 2026, 8:07 PM UTC
Fix✗ → ✓Nov 11, 2026, 8:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

cna.openjsf.org/security-advisories.html

Show all references (1 more)

nodejs.org/en/blog/vulnerability/november-2026-security-releases

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records