Skip to content
VulniPulse
High 2 vendors · 2 advisories

CVE-2026-123864: Node.js is vulnerable to cross-connection memory disclosure via TLS write re-entrancy in the HTTPS request parser

CVE-2026-123864 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
High
CVSS base score
7.4 (Red Hat)
CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H · base score 8.1, scored by openjsAttack vector: network. Attack complexity: high. Privileges required: none. User interaction: none. Scope: changed. Confidentiality impact: low. Integrity impact: low. Availability impact: high.
Weakness
  • CWE-416 Use After Free
EPSS
0.36% chance of exploitation in the next 30 days (31st percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
Fixed releases
  • Red Hat: nodejs24-main-24.22.3-0.1.hum1, nodejs22-main-10.9.9-1.22.23.5.2.3.2.3.1.hum1, nodejs22-main-22.23.5-2.3.2.3.1.hum1, nodejs26-main-11.20.0-1.26.13.1.0.1.hum1, nodejs24-main-11.19.1-1.24.22.3.0.1.hum1, nodejs26-main-26.13.1-0.1.hum1 and 1 more in the advisory
Vendor advisories
2 from NetApp, Red Hat
Assigned by
openjs (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-123864; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requests. TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes; if that write is issued from JavaScript running inside the HTTP parser's on_body callback, ClearOut() decrypts the next TLS record while the parser is still mid-body, re-entering llhttp_execute() and causing a use-after-free and an out-of-bounds heap read. The server then copies that freed or unrelated heap memory into the response for the request body. Triggering it requires a handler that calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk, and reading the leaked memory requires any ordinary route that echoes or stores a request body. Cleartext node:http is not affected. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Text from the CVE.org record (openjs).

How do I fix CVE-2026-123864?

Upgrade to a fixed release named by the vendor:

  • Red Hat: nodejs24-main-24.22.3-0.1.hum1, nodejs22-main-10.9.9-1.22.23.5.2.3.2.3.1.hum1, nodejs22-main-22.23.5-2.3.2.3.1.hum1, nodejs26-main-11.20.0-1.26.13.1.0.1.hum1, nodejs24-main-11.19.1-1.24.22.3.0.1.hum1, nodejs26-main-26.13.1-0.1.hum1
  • Offload TLS termination to a trusted reverse proxy or load balancer, and configure the Node.js application to serve traffic over cleartext HTTP bound only to localhost (127.0.0.1), as cleartext HTTP is not affected by this flaw. If TLS must remain terminated by the Node.js process, restrict network access to trusted hosts using firewall rules to limit exposure: # firewall-cmd --permanent --zone=internal --add-port= /tcp # firewall-cmd --permanent --zone=public --remove-port= /tcp # firewall-cmd --reload Caveats: Restricting access to trusted networks or localhost prevents untrusted remote clients from reaching the service. Offloading TLS requires reconfiguring traffic routing and reverse proxy endpoints. Warning: Modifying firewall configurations and running `firewall-cmd --reload` will reload firewall rule sets and may cause momentary disruptions to active connections. (Red Hat)

Vendor advisories for CVE-2026-123864

NetApp

1 advisory
  • Advisory severityHigh8.1

    High [CVE-2026-123863 +1] Node.js Vulnerability in NetApp Products

    NTAP-20261120-0007Source published Source updated

    This bulletin covers 2 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.

    Node.js versions 22.x prior to 22.23.5, 24.x prior to 24.22.3 and 26.x prior to 26.13.1 are susceptible to a vulnerability which when successfully exploited could allow an unauthenticated remote attacker to trigger unsafe memory handling during HTTPS request processing, potentially compromising process memory and affecting normal server operation. Successful exploitation of this vulnerability could lead to disclosure of sensitive information, addition or modification of data, or Denial of Service (DoS). NetApp reports that one or more additional products remain under investigation; review the canonical advisory for current status. NetApp states there is no workaround available at this time.

    Affected products in this advisory
    No product details extracted. Check the source bulletin.
    Source-reported affected versions
    • 22.23.5
    • 24.22.3
    • 26.13.1
    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    No mitigation guidance extracted; consult the source.

Red Hat

1 advisory
  • Advisory severityHigh7.4

    High [CVE-2026-123864] Information disclosure via HTTPS parser re-entrancy

    CVE-2026-123864Source published Source updated

    Information disclosure via HTTPS parser re-entrancy. Red Hat rates this important (CVSS 7.4). Weakness: CWE-416. Red Hat lists fixing advisory RHSA-2026:99433 with package nodejs24-main-24.22.3-0.1.hum1, nodejs22-main-10.9.9-1.22.23.5.2.3.2.3.1.hum1, nodejs22-main-22.23.5-2.3.2.3.1.hum1, nodejs26-main-11.20.0-1.26.13.1.0.1.hum1. Affected product named by the advisory: Red Hat Hardened Images.

    Related products — impact not confirmed
    • Red Hat Hardened Images
    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    • nodejs24-main-24.22.3-0.1.hum1
    • nodejs22-main-10.9.9-1.22.23.5.2.3.2.3.1.hum1
    • nodejs22-main-22.23.5-2.3.2.3.1.hum1
    • nodejs26-main-11.20.0-1.26.13.1.0.1.hum1

    3 more entries in the full advisory.

    Mitigation guidance
    • Offload TLS termination to a trusted reverse proxy or load balancer, and configure the Node.js application to serve traffic over cleartext HTTP bound only to localhost (127.0.0.1), as cleartext HTTP is not affected by this flaw. If TLS must remain terminated by the Node.js process, restrict network access to trusted hosts using firewall rules to limit exposure: # firewall-cmd --permanent --zone=internal --add-port=<PORT>/tcp # firewall-cmd --permanent --zone=public --remove-port=<PORT>/tcp # firewall-cmd --reload Caveats: Restricting access to trusted networks or localhost prevents untrusted remote clients from reaching the service. Offloading TLS requires reconfiguring traffic routing and reverse proxy endpoints. Warning: Modifying firewall configurations and running `firewall-cmd --reload` will reload firewall rule sets and may cause momentary disruptions to active connections.

References

Timeline

  1. CVE record published
  2. First vendor advisory listed by VulniPulse
  3. CVE record last updated

All NetApp advisories

Get an email when NetApp publishes the next one.

See NetApp's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about NetApp