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

nodejs node: Improper Authentication

nodejs · node

4.4MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 30 Jul 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.08% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • 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. Verify the installed build against the product-specific fixed version after deployment.
  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: No default targetRemediation target: Normal maintenance

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.18.1-r0Alpine Security Database ↗Source updated 3 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.2-r0Alpine Security Database ↗Source updated 3 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.2-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.20.19.2+dfsg-1+deb13u3Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.18.20.4+dfsg-1~deb12u3Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.24.19.0+dfsg+~cs24.13.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.24.19.0+dfsg+~cs24.13.3-1Debian Security Tracker ↗Source updated 5 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 5 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.

2 current
CVE-2026-56850 · CSAF 2.0 · revision 17 · interimSUSE Product Security TeamCVE-2026-56850
144 known affected

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

  • nodejs10 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs10-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs10-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs8 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs8-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs8-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • npm10 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • npm8 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs10 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs10-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs10-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs12 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
Summary
A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requests configured with different client certificates. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-56850 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitynodejs: Node.js: mTLS client identities can be reused due to HTTPS Agent connection flaw
56 known affected

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

  • nodejs as a component of Red Hat Enterprise Linux 10
  • nodejs-devel as a component of Red Hat Enterprise Linux 10
  • nodejs-docs as a component of Red Hat Enterprise Linux 10
  • nodejs-full-i18n as a component of Red Hat Enterprise Linux 10
  • nodejs-libs as a component of Red Hat Enterprise Linux 10
  • nodejs-npm as a component of Red Hat Enterprise Linux 10
  • nodejs22.src as a component of Red Hat Enterprise Linux 10
  • nodejs24 as a component of Red Hat Enterprise Linux 10
  • nodejs24-devel as a component of Red Hat Enterprise Linux 10
  • nodejs24-docs as a component of Red Hat Enterprise Linux 10
  • nodejs24-full-i18n as a component of Red Hat Enterprise Linux 10
  • nodejs24-libs as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in Node.js. The HTTPS Agent, responsible for managing secure connections, can incorrectly reuse client identities across different requests. This occurs due to a technical issue with PFX object-array key collisions during connection reuse. As a result, a client's identity, established through mutual TLS (mTLS) authentication, could be mistakenly applied to another request, potentially leading to unauthorized access or identity spoofing.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
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.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-51020

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requests configured with different client certificates. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

What

A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requests configured with different client certificates. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

Why

The affected component does not establish the requesting party's identity reliably before granting access.

How

An attacker operating through local access may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requests configured with different client certificates. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.

Why

The affected component does not establish the requesting party's identity reliably before granting access.

How

An attacker operating through local access may attempt exploitation with elevated privileges. 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
local access → Improper Authentication → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
High: elevated access is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
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-287 ↗

CWE-287: Improper Authentication. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

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

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.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
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-287
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2585Node.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 Dateien zu manipulieren.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260805Security Bulletin 5 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 5 Aug 2026, published on 5 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0947Multiples vulnérabilités dans Node.js

De multiples vulnérabilités ont été découvertes dans Node.js. Certaines d'entre elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-030343Node.js FoundationのNode.jsにおける認証に関する脆弱性

Node.jsのHTTPSエージェントにおける接続再利用の欠陥により、PFXオブジェクト配列のキーが衝突し、異なるクライアント証明書で設定されたリクエスト間で相互TLS（mTLS）クライアントの識別情報が再利用される可能性があります。この脆弱性はNode.jsの**26.x**、**24.x**、**22.x**の各バージョンに影響を及ぼします。

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.
Patch available
Affected
Fixed
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 30 Jul 2026 · Last source change 30 Jul 2026, 12:37 UTC · CWE-287 · Improper Authentication

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-51020
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD enriched

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    26.5.0 ≤ 26.5.0; 24.18.0 ≤ 24.18.0; 22.23.1 ≤ 22.23.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    26.5.0 ≤ 26.5.0; 24.18.0 ≤ 24.18.0; 22.23.1 ≤ 22.23.1 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: nodejs.org/july-2026-security-releases.
    Before
    no authoritative guidance recorded
    After
    vendor advisory: nodejs.org/july-2026-security-releases
    support@hackerone.com ↗
  4. CVSS scoreCVSS score changed from 4.1 (CVSS 3.0 · CNA · CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N) to 4.4 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N).
    Before
    4.1 (CVSS 3.0 · CNA · CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N)
    After
    4.4 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N)
    NIST NVD ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-51020↗Vendor CSAF · SUSE Product Security Team↗Red Hat Product Security security advisory↗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-56850 · cve.blacktree.nl