Improper Certificate Validation Affecting nodejs26 package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.21% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-NODEJS26-22438040
  • published12 Nov 2026
  • disclosed11 Nov 2026

Introduced: 11 Nov 2026

NewCVE-2026-123877  (opens in a new tab)
CWE-295  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 nodejs26.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs26 package and not the nodejs26 package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

CVSS Base Scores

version 3.1