Description
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**.
Published: 2026-07-30
Score: 4.1 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A flaw in Node.js HTTPS Agent connection reuse causes PFX object-array key collisions, enabling mutual TLS (mTLS) client identities to be reused across requests that are configured with different client certificates. This allows an attacker to impersonate a legitimate client and gain unauthorized access to protected resources, potentially leading to confidentiality and integrity breach. The weakness is classified as Authentication Failure (CWE‑287) and improper credential or key management (CWE‑303).

Affected Systems

Node.js runtimes version 26.x, 24.x, and 22.x are affected. Servers, APIs, and services running these Node.js releases that make outbound HTTPS client connections with mTLS are at risk.

Risk and Exploitability

The vulnerability has a CVSS score of 4.1, indicating a moderate impact, and an EPSS score of less than 1%, suggesting low exploitation probability. It is not listed in CISA KEV. The likely attack vector relies on the ability of an attacker to influence HTTPS client requests—either by compromising the application code, submitting crafted requests to the Node.js process, or manipulating certificate selection. Given the low EPSS and moderate CVSS, the risk is considered low to moderate.

Generated by OpenCVE AI on August 2, 2026 at 05:36 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to a patched Node.js release that resolves the HTTPS Agent connection reuse flaw
  • Configure the HTTPS Agent to disable connection reuse or create a new agent per client certificate
  • Implement strict validation to ensure that client certificates are not reused across distinct requests

Generated by OpenCVE AI on August 2, 2026 at 05:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 31 Jul 2026 00:15:00 +0000

Type Values Removed Values Added
Title nodejs: Node.js: mTLS client identities can be reused due to HTTPS Agent connection flaw
First Time appeared Redhat
Redhat hummingbird
Weaknesses CWE-303
CPEs cpe:/a:redhat:hummingbird:1
Vendors & Products Redhat
Redhat hummingbird
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.1, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N'}

threat_severity

Moderate


Thu, 30 Jul 2026 13:45:00 +0000

Type Values Removed Values Added
First Time appeared Nodejs
Nodejs nodejs
Vendors & Products Nodejs
Nodejs nodejs

Thu, 30 Jul 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 30 Jul 2026 06:15:00 +0000

Type Values Removed Values Added
Description 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**.
Weaknesses CWE-287
References
Metrics cvssV3_0

{'score': 4.1, 'vector': 'CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: hackerone

Published:

Updated: 2026-07-30T12:37:10.100Z

Reserved: 2026-06-23T15:00:03.632Z

Link: CVE-2026-56850

cve-icon Vulnrichment

Updated: 2026-07-30T12:36:54.201Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-07-30T06:25:55.073

Modified: 2026-07-30T16:33:59.580

Link: CVE-2026-56850

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-07-30T06:02:50Z

Links: CVE-2026-56850 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-02T05:45:03Z

Weaknesses
  • CWE-287

    Improper Authentication

  • CWE-303

    Incorrect Implementation of Authentication Algorithm