ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-123877

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.

Published Nov 11, 2026 · catalog updated Nov 12, 2026 · Red Hat Red Hat Enterprise Linux

Last checked Nov 12, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-123877. A missing EPSS score is not a low risk. Compare Red Hat Red Hat Enterprise Linux with the linked advisory before you change production.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.

Same product and reporting

Severity
Medium6.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Not in the current FIRST EPSS dataset
Remediation
Advisory link
Affected products
Alpine:v3.21 nodejs · Alpine:v3.22 nodejs · Alpine:v3.23 nodejs · Alpine:v3.24 nodejs

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Alpine:v3.21 nodejs0 → 22.23.5-r0
  • Alpine:v3.22 nodejs0 → 22.23.5-r0
  • Alpine:v3.23 nodejs0 → 24.22.3-r0
  • Alpine:v3.24 nodejs0 → 24.22.3-r0

How to fix CVE-2026-123877

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for CVE-2026-123877. A missing EPSS score is not a low risk. Compare Red Hat Red Hat Enterprise Linux with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0 → 22.23.5-r0, 0 → 24.22.3-r0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-295: Improper Certificate Validation. EPSS is absent from the current FIRST dataset. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Nov 11, 2026 · Red Hat Security Data

    Detected

    nodejs: nodejs: Certificate validation bypass via TLS session cache reuse

  2. Nov 12, 2026 · Trivy Vulnerability DB

    Fix available

    nodejs fixed in 22.23.5-r0; nodejs fixed in 22.23.5-r0; nodejs fixed in 24.22.3-r0; nodejs fixed in 24.22.3-r0

  3. Nov 12, 2026 · Trivy Vulnerability DB

    Fix available

    nodejs fixed in 22.23.5-r0

  4. Nov 12, 2026 · Trivy Vulnerability DB

    Fix available

    nodejs fixed in 24.22.3-r0

  5. Nov 12, 2026 · Trivy Vulnerability DB

    Updated

    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

Sources

  • Red Hat Security DataVendor advisoryCVE-2026-123877

    nodejs: nodejs: Certificate validation bypass via TLS session cache reuse

    access.redhat.com
  • Trivy Vulnerability DBPackage advisoryALPINE-CVE-2026-123877

    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

    osv.dev

References

Freshness

Last verified in this catalog Nov 12, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Trivy Vulnerability DBNov 12, 2026
  • Red Hat Security DataNov 12, 2026