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

CVE-2026-106069: A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the…

HighCVSS 7.4 · v3.0—Proof of concept Fix available

Noroxi assessment

Priority: Monitor (action score 29/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: azl3 nodejs 24.21.0-1 on Azure Linux 3.0 24.22.1-0.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to azl3 nodejs 24.21.0-1 on Azure Linux 3.0 24.22.1-0 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 flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the client connected to, when the host is a non-canonical IPv4 literal with a leading zero, such as `0127.0.0.1`. `tls.checkServerIdentity()` normalizes the host following the WHATWG URL rules, which read a leading-zero octet as octal (`0127.0.0.1` becomes `87.0.0.1`), while the connection is made through the operating system resolver, which on some platforms such as macOS reads it as decimal (`127.0.0.1`). A server at the connected address can then be authenticated with a certificate issued for another IP address. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

Published: Oct 23, 2026
Updated: Nov 2, 2026
EPSS: 0.3% · 23th percentile
CWE: CWE-295

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 29 / 40 · 7.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · hackerone: 7.4; 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
Proof of concept exists, no weaponized module
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 (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

nodejs node
- 22.23.3 and later · up to and including 22.23.3affected · semver
- 24.22.0 and later · up to and including 24.22.0affected · semver
- 26.12.0 and later · up to and including 26.12.0affected · semver

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
AlmaLinux:10	nodejs	before 1:22.23.4-1.el10_2	1:22.23.4-1.el10_2
AlmaLinux:10	nodejs-devel	before 1:22.23.4-1.el10_2	1:22.23.4-1.el10_2
AlmaLinux:10	nodejs-docs	before 1:22.23.4-1.el10_2	1:22.23.4-1.el10_2
AlmaLinux:10	nodejs-full-i18n	before 1:22.23.4-1.el10_2	1:22.23.4-1.el10_2
AlmaLinux:10	nodejs-libs	before 1:22.23.4-1.el10_2	1:22.23.4-1.el10_2
AlmaLinux:10	nodejs-npm	before 1:10.9.9-1.22.23.4.1.el10_2	1:10.9.9-1.22.23.4.1.el10_2
AlmaLinux:10	nodejs24	before 1:24.22.1-3.el10_2	1:24.22.1-3.el10_2
AlmaLinux:10	nodejs24-devel	before 1:24.22.1-3.el10_2	1:24.22.1-3.el10_2
AlmaLinux:10	nodejs24-docs	before 1:24.22.1-3.el10_2	1:24.22.1-3.el10_2
AlmaLinux:10	nodejs24-full-i18n	before 1:24.22.1-3.el10_2	1:24.22.1-3.el10_2
AlmaLinux:10	nodejs24-libs	before 1:24.22.1-3.el10_2	1:24.22.1-3.el10_2
AlmaLinux:10	nodejs24-npm	before 2:11.19.1-1.24.22.1.3.el10_2	2:11.19.1-1.24.22.1.3.el10_2
AlmaLinux:8	nodejs	before 1:24.22.1-1.module_el8.10.0+4331+0683c9c1	1:24.22.1-1.module_el8.10.0+4331+0683c9c1
AlmaLinux:8	nodejs-devel	before 1:24.22.1-1.module_el8.10.0+4331+0683c9c1	1:24.22.1-1.module_el8.10.0+4331+0683c9c1
AlmaLinux:8	nodejs-docs	before 1:24.22.1-1.module_el8.10.0+4331+0683c9c1	1:24.22.1-1.module_el8.10.0+4331+0683c9c1
AlmaLinux:8	nodejs-full-i18n	before 1:24.22.1-1.module_el8.10.0+4331+0683c9c1	1:24.22.1-1.module_el8.10.0+4331+0683c9c1
AlmaLinux:8	nodejs-libs	before 1:24.22.1-1.module_el8.10.0+4331+0683c9c1	1:24.22.1-1.module_el8.10.0+4331+0683c9c1
AlmaLinux:8	nodejs-nodemon	before 3.1.14-2.module_el8.10.0+4250+09238ed4	3.1.14-2.module_el8.10.0+4250+09238ed4
AlmaLinux:8	nodejs-packaging	before 2021.06-6.module_el8.10.0+4086+70facd4a	2021.06-6.module_el8.10.0+4086+70facd4a
AlmaLinux:8	nodejs-packaging-bundler	before 2021.06-6.module_el8.10.0+4086+70facd4a	2021.06-6.module_el8.10.0+4086+70facd4a
AlmaLinux:8	npm	before 1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1	1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1
AlmaLinux:8	v8-13.6-devel	before 3:13.6.233.17-1.24.22.1.1.module_el8.10.0+4331+0683c9c1	3:13.6.233.17-1.24.22.1.1.module_el8.10.0+4331+0683c9c1
AlmaLinux:9	nodejs	before 1:24.22.1-3.module_el9.8.0+333+788f3075	1:24.22.1-3.module_el9.8.0+333+788f3075
AlmaLinux:9	nodejs-devel	before 1:24.22.1-3.module_el9.8.0+333+788f3075	1:24.22.1-3.module_el9.8.0+333+788f3075

+36

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-105482Oct 23, 2026 · A flaw in Node.js DNS resolution allows hostnames containing a NUL byte to be silently truncated by the dns.resolve*() functions and…
29Monitor
← EarlierCVE-2026-105483Oct 23, 2026 · A flaw in Node.js TLS hostname verification allows a certificate without a matching IP address SAN to authenticate a connection to an IPv4…
29Monitor
Later →CVE-2026-106070Oct 23, 2026 · A flaw in the Node.js `zlib.ZipFile` API can cause it to return bytes that do not belong to the requested entry after the local and central…
14Monitor

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
azl3 nodejs 24.21.0-1 on Azure Linux 3.0	24.22.1-0 · Release Notes	Microsoft (MSRC)
almalinux:nodejs	1:24.22.1-1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs-devel	1:24.22.1-1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs-docs	1:24.22.1-1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs-full-i18n	1:24.22.1-1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs-libs	1:24.22.1-1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs-nodemon	3.1.14-2.module_el8.10.0+4250+09238ed4 · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs-packaging	2021.06-6.module_el8.10.0+4086+70facd4a · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs-packaging-bundler	2021.06-6.module_el8.10.0+4086+70facd4a · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs24	1:24.22.1-3.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:nodejs24-devel	1:24.22.1-3.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:npm	1:11.19.1-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8	Package registry (OSV)
almalinux:v8-13.6-devel	3:13.6.233.17-1.24.22.1.1.module_el8.10.0+4331+0683c9c1 · AlmaLinux:8	Package registry (OSV)
alpine:nodejs	22.23.4-r0 · Alpine:v3.21	Package registry (OSV)
alpine:nodejs-current	26.12.1-r0 · Alpine:v3.24	Package registry (OSV)
debian:nodejs	24.22.1+dfsg+~cs24.19.2-1 · Debian:14	Package registry (OSV)
opensuse:nodejs22	22.23.4-160000.1.1 · openSUSE:Leap 16.0	Package registry (OSV)
opensuse:nodejs24	24.22.1-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
rocky linux:nodejs	1:24.22.1-3.module+el9.8.0+40401+e24b8c95 · Rocky Linux:9	Package registry (OSV)
rocky linux:nodejs-nodemon	0:3.1.14-2.module+el8.10.0+40277+b1b3f89e · Rocky Linux:8	Package registry (OSV)
rocky linux:nodejs-packaging	0:2021.06-6.module+el8.10.0+40048+6d99f608 · Rocky Linux:8	Package registry (OSV)
rocky linux:nodejs22	1:22.23.4-1.el10_2 · Rocky Linux:10	Package registry (OSV)
rocky linux:nodejs24	1:24.22.1-3.el10_2 · Rocky Linux:10	Package registry (OSV)
suse:nodejs22	22.23.4-150600.13.27.1 · SUSE:Linux Enterprise Server 15 SP6-LTSS	Package registry (OSV)
suse:nodejs22	22.23.4-160000.1.1 · SUSE:Linux Enterprise Server 16.0	Package registry (OSV)
suse:nodejs24	24.22.1-150700.15.21.1 · SUSE:Linux Enterprise Module for Web and Scripting 15 SP7	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2026-10-23

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.

First PoCOct 23, 2026-1 d
PublishedOct 23, 2026
Fix recordedOct 25, 2026+1 d
TodayNov 13, 2026+21 d

EPSS, last 120 days

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

Variant candidates

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

CVE-2026-1054830 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-12387719 days apartNode.js is vulnerable to a certificate validation bypass in https.Agent via cross-policy TLS session reuse
27Monitor
CVE-2026-1060720 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
CVE-2026-12386719 days apartNode.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CA
16Monitor

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.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-1388 · Oct 23, 2026(Node.js Projesi Güvenlik Bildirimi)

All national notices →

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

Technical details

Attack conditions

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

If successful

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

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

Weakness class (CWE)

CWE-295 · Improper Certificate Validation

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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

SSVC exploitation— → noneNov 2, 2026, 3:07 PM UTC
Fix✗ → ✓Oct 25, 2026, 3:40 AM UTC
Exploit maturitynone → pocOct 24, 2026, 3:39 AM UTC
Exploit maturity— → noneOct 23, 2026, 6:07 PM UTC

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

References

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

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

All records

Noroxi analysis

What does it mean in your environment?

We use this product, ask for help

Data sources and verification

CNA: hackerone

CVE.org (CNA)Nov 2, 2026, 1:31 PM UTC
CISA ADPNov 2, 2026, 1:31 PM UTC
NVDNov 2, 2026, 2:17 PM UTC
FIRST EPSSNov 12, 2026, 12:00 AM UTC
OSV / GHSANov 13, 2026, 3:18 AM UTC
MSRCNov 13, 2026, 3:25 AM UTC
PoC-in-GitHubNov 13, 2026, 3:18 AM UTC

Each line is when that source was last processed for this record.

CVE-2026-106069: A flaw in Node.js TLS hostname verification can cause a server certificate to be validated against a different IP address than the one the…

Noroxi assessment

Get told when this record changes

Follow CVE-2026-106069

What does it mean in your environment?

Affected systems

Is your version affected?

Watch new CVEs for node

Versions reported by the vendor

Package-level exposure

Same product

Remediation

Which version to upgrade to

Exploit status

Research context

Timeline

Variant candidates

National notice (Türkiye Cybersecurity Directorate / USOM)

Technical details

Attack conditions

If successful

Root cause

The bug in code

Attack context

Change log

References