BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-106069High confidence

nodejs node: Improper Certificate Validation

nodejs · node

7.4HighCVSS 3.0
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs nodejs node and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.24.22.1-r0Alpine Security Database ↗Source updated 23 Oct 2026
Alpine v3.22v3.22 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.22.23.4-r0Alpine Security Database ↗Source updated 23 Oct 2026
Alpine v3.21v3.21 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.22.23.4-r0Alpine Security Database ↗Source updated 23 Oct 2026
Debian trixietrixie · sourcenodejsAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 23 Oct 2026
Debian bookwormbookworm · sourcenodejsAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 23 Oct 2026
Debian forkyforky · sourcenodejsAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 23 Oct 2026
Debian sidsid · sourcenodejsAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 23 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivenodejsUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 23 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-106069 · CSAF 2.0 · revision 3 · interimSUSE Product Security TeamCVE-2026-106069
20 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SUSE Linux Enterprise Module for Web and Scripting 15 SP7:nodejs22
  • SUSE Linux Enterprise Module for Web and Scripting 15 SP7:nodejs22-devel
  • SUSE Linux Enterprise Module for Web and Scripting 15 SP7:nodejs22-docs
  • SUSE Linux Enterprise Module for Web and Scripting 15 SP7:npm22
  • SUSE Linux Enterprise Server 15 SP6-LTSS:nodejs22
  • SUSE Linux Enterprise Server 15 SP6-LTSS:nodejs22-devel
  • SUSE Linux Enterprise Server 15 SP6-LTSS:nodejs22-docs
  • SUSE Linux Enterprise Server 15 SP6-LTSS:npm22
  • SUSE Linux Enterprise Server 15 SP7:nodejs22
  • SUSE Linux Enterprise Server 15 SP7:nodejs22-devel
  • SUSE Linux Enterprise Server 15 SP7:nodejs22-docs
  • SUSE Linux Enterprise Server 15 SP7:npm22
Summary
unknown
Remediation
No remediation text is recorded.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
01

What, why and how

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**.

What

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**.

Why

The product does not validate, or incorrectly validates, a certificate.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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**.

Why

The product does not validate, or incorrectly validates, a certificate.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Certificate Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-295 ↗

CWE-295: Improper Certificate Validation. The product does not validate, or incorrectly validates, a certificate.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Common Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-295
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-4117Node.js: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um einen Denial of Service Angriff durchzuführen, um Sicherheitsvorkehrungen zu umgehen und um beliebigen Programmcode auszuführen.

Official advisory ↗
CSIRT Italia · Italian · node.js-risolte-molteplici-vulnerabilita-1Node.js: risolte molteplici vulnerabilità

Rilasciati aggiornamenti di sicurezza che risolvono 10 vulnerabilità, di cui 4 con gravità “alta”, in Node.js, noto software open source per l’esecuzione di codice Javascript. Tali vulnerabilità, qualora sfruttate, potrebbero consentire ad un utente malintenzionato remoto l'elusione dei meccanismi di sicurezza e/o l'esecuzione di codice arbitrario sui sistemi interessati.

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-7011Node.js 제품 보안 업데이트 권고

Node.js에서 발생하는 Improper Validation of Certificate with Host Mismatch 취약점(CVE-2026-106069) [1]

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
  • SUSE Linux Enterprise Module for Web and Scripting 15 SP7:nodejs22
  • SUSE Linux Enterprise Module for Web and Scripting 15 SP7:nodejs22-devel
  • SUSE Linux Enterprise Module for Web and Scripting 15 SP7:nodejs22-docs
  • SUSE Linux Enterprise Module for Web and Scripting 15 SP7:npm22
  • SUSE Linux Enterprise Server 15 SP6-LTSS:nodejs22
  • SUSE Linux Enterprise Server 15 SP6-LTSS:nodejs22-devel
  • SUSE Linux Enterprise Server 15 SP6-LTSS:nodejs22-docs
  • SUSE Linux Enterprise Server 15 SP6-LTSS:npm22
  • SUSE Linux Enterprise Server 15 SP7:nodejs22
  • SUSE Linux Enterprise Server 15 SP7:nodejs22-devel
  • SUSE Linux Enterprise Server 15 SP7:nodejs22-docs
  • SUSE Linux Enterprise Server 15 SP7:npm22
  • SUSE Linux Enterprise Server for SAP Applications 15 SP6:nodejs22
  • SUSE Linux Enterprise Server for SAP Applications 15 SP6:nodejs22-devel
  • SUSE Linux Enterprise Server for SAP Applications 15 SP6:nodejs22-docs
  • SUSE Linux Enterprise Server for SAP Applications 15 SP6:npm22
  • SUSE Linux Enterprise Server for SAP Applications 15 SP7:nodejs22
  • SUSE Linux Enterprise Server for SAP Applications 15 SP7:nodejs22-devel
  • SUSE Linux Enterprise Server for SAP Applications 15 SP7:nodejs22-docs
  • SUSE Linux Enterprise Server for SAP Applications 15 SP7:npm22
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 23 Oct 2026 · Last source change 23 Oct 2026, 16:15 UTC · CWE-295 · Improper Certificate Validation

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
Unavailable
European sourceNo official EUVD mapping
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: removed mitigation: acn.gov.it/node.js-risolte-molteplici-vulnerabilita-1; removed remediation: acn.gov.it/node.js-risolte-molteplici-vulnerabilita-1.
    Before
    mitigation: acn.gov.it/node.js-risolte-molteplici-vulnerabilita-1 · remediation: acn.gov.it/node.js-risolte-molteplici-vulnerabilita-1
    After
    no authoritative guidance recorded
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    The authority advisory does not provide a concise affected-product range. · Fixed: The authority publishes remediation guidance. Confirm the exact fixed release in the linked primary advisory.
    After
    node: 22.23.3 ≤ 22.23.3, 24.22.0 ≤ 24.22.0, 26.12.0 ≤ 26.12.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  3. Remediation statusRemediation status changed from Mitigation available to Awaiting fix.
    Before
    Mitigation available
    After
    Awaiting fix
    CNA ↗
  4. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CNA ↗
  5. CVSS scoreCVSS score changed from not recorded to 7.4 (CVSS 3.0 · CNA · CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).
    Before
    not recorded
    After
    7.4 (CVSS 3.0 · CNA · CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N)
    CNA ↗
  6. Catalogue recordCVE added to the BlackTree catalogue.
    Official national cybersecurity authority ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-106069 · cve.blacktree.nl