Skip to main content
Mallory
← Back to News
open-source-dependency-vulnerabilityinternet-facing-service-vulnerabilityidentity-authentication-vulnerabilitywidely-deployed-product-advisory

Node.js Patches 16 Flaws Enabling Remote Crashes, Memory Leaks and TLS Authentication Bypasses

Vulnerability Disclosure · 38 sources · Updated 4d ago · First seen Nov 11, 2026

Node.js Patches 16 Flaws Enabling Remote Crashes, Memory Leaks and TLS Authentication Bypasses

Node.js released versions 22.23.5, 24.22.3 and 26.13.1 to address 16 vulnerabilities, including seven rated high severity. HTTP/2 flaws can allow unauthenticated attackers to crash servers, corrupt memory or expose data from other connections under affected configurations. CVE-2026-123866 can leak response buffers during stream teardown; CVE-2026-123863 can terminate servers through a session-teardown assertion failure; and CVE-2026-123874 introduces a use-after-free when applications serve files over HTTP/2. Some attack paths affect only recent Node.js 24 and 26 releases, while others also affect Node.js 22. Additional fixes address hostname-specific mutual-TLS authorization bypasses, proxy credentials exposed in error messages, and a macOS/Windows permission bypass that reveals filenames rather than file contents. Potential memory exposure includes requests, responses and TLS private keys, according to reporting on the release; exploitation has not been reported.

Prioritize upgrading internet-facing HTTP/2 services and applications using hostname-specific client-certificate policies. The release guidance identifies updating as the only fix and provides no workaround; end-of-life release lines receive no fixes in this release. Amazon Linux records listed fixes as pending for several affected packages at disclosure, so administrators should verify package-specific advisory status. Separately, Red Hat issued Important-rated Node.js 26 updates for RHEL 9 and 10 covering broader batches of 26 and 31 vulnerabilities, respectively; those advisories should not be assumed to resolve every newly disclosed flaw. Okta and Auth0 are patching their cloud environments and report no evidence of exploitation. Auth0 Actions customers should move to Node 22 and deploy changes unless already using Node 22; customers using either company's Node.js SDKs should update their runtime to the latest patched version.

Do you run this?See affected versions and whether adversaries are exploiting it.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

16 events · Jun 26, 2026 – Nov 11, 2026
  1. Reported Nov 12, 20266d ago

    Node.js releases patched versions 22.23.5, 24.22.3, and 26.13.1

    Node.js released updates fixing the 16 vulnerabilities across its three supported release lines. The security advisory identifies updating as the only fix, offers no workaround, and provides no fixes for end-of-life branches such as 20.x and 25.x.

    Node.js Fixes 16 Flaws, Including HTTP/2 Bugs That Crash Servers and Leak Other Connections' Data
  2. Reported Nov 11, 20267d ago

    Amazon Linux fixes Node.js HTTP/2 memory and file-descriptor leak

    Amazon Linux released fixes for CVE-2026-123865 in Amazon Linux 2023's nodejs22 and nodejs24 packages through ALAS2023-2026-3456 and ALAS2023-2026-3457. The flaw lets unauthenticated HTTP/2 clients permanently leak server memory and file descriptors by triggering protocol errors during session shutdown; a fix for Amazon Linux 2027 Preview's nodejs24 remained pending.

    CVE-2026-123865
  3. Reported Nov 11, 20267d ago

    Amazon Linux fixes Node.js HTTP/2 file-transfer crash vulnerability

    Amazon Linux released fixes for CVE-2026-123875 in Amazon Linux 2023's nodejs22 and nodejs24 packages through ALAS2023-2026-3456 and ALAS2023-2026-3457. The flaw lets unauthenticated clients crash HTTP/2 servers by cancelling file downloads; a fix for Amazon Linux 2027 Preview's nodejs24 remained pending.

    CVE-2026-123875
  4. Reported Nov 11, 20267d ago

    Amazon Linux releases fixes for Node.js HTTPS memory disclosure

    Amazon Linux released advisories ALAS2023-2026-3456 and ALAS2023-2026-3457, fixing CVE-2026-123864 in Amazon Linux 2023's nodejs22 and nodejs24 packages. The flaw allows unauthenticated clients to read other connections' memory, potentially including TLS private keys; a fix for Amazon Linux 2027 Preview's nodejs24 remained pending.

    CVE-2026-123864
  5. Reported Nov 11, 20267d ago

    Okta and Auth0 begin cloud patching and issue Node.js runtime guidance

    Okta and Auth0 said they were applying patches across their Cloud Services environments following the November 11 disclosures and had observed no evidence of exploitation. They advised SDK customers to install patched Node.js runtimes and Auth0 Actions customers not already on Node 22 to upgrade and deploy their changes.

    Node.js Project: November 11 Security Releases | Okta Security
  6. Nov 11, 20267d ago

    Amazon Linux discloses Node.js HTTP/2 server memory-exhaustion vulnerability

    Amazon Linux disclosed CVE-2026-123868, a medium-severity flaw affecting Node.js 24.x and 26.x that lets unauthenticated HTTP/2 clients exhaust server memory through queued DATA frames outside session memory accounting. Fixes were pending for nodejs24 on Amazon Linux 2023 and Amazon Linux 2027 Preview; Amazon Linux 2023's nodejs22 package was unaffected.

    CVE-2026-123868
  7. Nov 11, 20267d ago

    Amazon Linux discloses Node.js TLS renegotiation authentication bypass

    Amazon Linux disclosed CVE-2026-123872, an Important-severity Node.js flaw allowing clients to change hostnames during TLS 1.2 renegotiation and bypass stricter client-certificate policies. Fixes were pending for nodejs22 and nodejs24 on Amazon Linux 2023 and nodejs24 on Amazon Linux 2027 Preview; no fixes were planned for Amazon Linux 2023's nodejs and nodejs20 packages.

    CVE-2026-123872
  8. Nov 11, 20267d ago

    Amazon Linux discloses Node.js TLS session certificate-validation bypass

    Amazon Linux disclosed CVE-2026-123877, an Important-severity Node.js flaw allowing cached TLS sessions authenticated under a broader CA policy to bypass a later request's stricter policy, potentially exposing confidential data. Fixes were pending for nodejs22 and nodejs24 on Amazon Linux 2023 and nodejs24 on Amazon Linux 2027 Preview.

    CVE-2026-123877
  9. Nov 11, 20267d ago

    Amazon Linux discloses exposure to Node.js zlib process-crash vulnerability

    Amazon Linux published CVE-2026-123862, a medium-severity flaw that can terminate a Node.js process when a peer disconnects while an application calls deflate.params() during streaming. It listed fixes as pending for nodejs22 and nodejs24 on Amazon Linux 2023 and nodejs24 on Amazon Linux 2027 Preview.

    CVE-2026-123862
  10. Nov 11, 20267d ago

    Node.js security disclosures reveal 16 flaws, including server memory leaks

    The November 11 disclosures covered 16 vulnerabilities, including HTTP/2 crashes and memory corruption, cross-connection memory disclosure, hostname-specific client-certificate bypasses, proxy credential exposure, and a recursive file-watching permission bypass. Seven flaws were rated high; exploitation of some server flaws could expose other users' requests, response data, or TLS private keys.

    Node.js Project: November 11 Security Releases | Okta Security
  11. Nov 11, 20267d ago

    Red Hat releases nodejs26 update addressing 31 vulnerabilities in RHEL 10

    Red Hat issued Important-rated advisory RHSA-2026:98619 for vulnerabilities in Node.js, undici, and brace-expansion. The update rebases nodejs26 to 26.12.1 and supplies release 26.12.1-3.el10_3 for x86_64, s390x, ppc64le, and aarch64.

    RHSA-2026:98619 - Security Advisory - Red Hat Customer Portal
  12. Nov 10, 20268d ago

    Red Hat releases Important-rated Node.js 26 security update for RHEL 9

    Red Hat issued RHSA-2026:97855, addressing 26 Node.js and undici vulnerabilities involving permission bypasses, information disclosure, TLS authentication failures, request smuggling, and denial of service. The update supplies package version 26.8.2-1.module+el9.9.0+24929+16cef9a5 for four architectures.

    RHSA-2026:97855 - Security Advisory - Red Hat Customer Portal
  13. Jul 2026

    Red Hat publishes Node.js fixes for RHEL 8, 9, and 10

    Red Hat published six errata addressing Node.js vulnerabilities including CVE-2026-48930 across RHEL 8, 9, and 10. The linked errata also addressed the HTTP/2 ORIGIN-frame denial of service and unauthorized file metadata modification flaws.

    2493326 - (CVE-2026-48930) CVE-2026-48930 nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling
  14. Jun 26, 20265mo ago

    Red Hat records Node.js read-only file metadata permission bypass

    Red Hat recorded CVE-2026-48935 as Bug 2493329 and assigned it low severity. The Node.js Permission API flaw allows unauthorized metadata changes on paths configured as read-only and affects Node.js 22, 24, and 26.

    2493329 - (CVE-2026-48935) CVE-2026-48935 nodejs: Node.js: Unauthorized file metadata modification
  15. Jun 26, 20265mo ago

    Red Hat records embedded-NUL hostname flaw in Node.js TLS handling

    Red Hat recorded CVE-2026-48930 as Bug 2493326. Embedded-NUL hostnames can cause C-string truncation in resolver bindings and silent authority rebinding in Node.js 22, 24, and 26.

    2493326 - (CVE-2026-48930) CVE-2026-48930 nodejs: Node.js: Silent authority rebinding due to embedded-nul hostnames in TLS handling
  16. Jun 26, 20265mo ago

    Red Hat records Node.js HTTP/2 ORIGIN-frame denial-of-service vulnerability

    Red Hat recorded CVE-2026-48619 as Bug 2493325. A malicious server can exhaust a Node.js HTTP/2 client's memory by sending unlimited ORIGIN frames; the issue affects Node.js 22, 24, and 26.

    2493325 - (CVE-2026-48619) CVE-2026-48619 nodejs: Node.js: Denial of Service via unlimited HTTP/2 ORIGIN frames
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.