SecOraLens
HighBreach

Node.js Fixes 16 Security Flaws That Could Expose TLS Private Keys and Crash Servers Remotely

Cyber Security News·Source published ·1 min read

What happened?

The Node.js project has released fixes for 16 security flaws across its 22.x, 24.x and 26.x lines. Seven are rated high, six medium, and three low. The official advisory says the patched builds are v22.23.5, v24.22.3 and v26.13.1. The update also refreshes three bundled parts: llhttp, undici, and sqlite. Memory Leak Could Expose TLS Private Keys The high-severity flaw is CVE-2026-123864. It affects the HTTPS code in all three lines. A client with no login can read memory that belongs to other connections. That memory can hold TLS private keys and other users’ requests.

Key details

  • Node.js released security updates fixing 16 vulnerabilities across the 22.x, 24.x, and 26.x release lines.
  • Seven flaws are rated high severity, six medium, and three low severity according to the official advisory.
  • CVE-2026-123864 allows unauthenticated clients to read heap memory containing TLS private keys and other users' requests via a zero-length TLS write re-entry issue.
  • TLS 1.2 renegotiation flaw lets clients change servername and bypass client certificate verification requirements.
  • https.Agent reuses cached TLS sessions across different CA policies, incorrectly reporting authorized === true for stricter validation requests.
  • Proxy credentials are exposed in ERR_PROXY_INVALID_CONFIG error messages, leaking secrets into logs and crash reports.

What is affected?

  • Node.js 22.x, 24.x, and 26.x release lines are affected by the vulnerabilities.

How do I fix or mitigate it?

  1. Teams that served traffic from vulnerable HTTPS handlers should consider replacing TLS private keys due to potential memory leaks.

What should defenders look for?

  • Proxy credentials appearing in ERR_PROXY_INVALID_CONFIG error logs indicate CVE-2026-123871 information disclosure.

Summarised by SecOraLens from Cyber Security News. Always read the original source before acting. How SecOraLens verifies advisories.

What to do next

For CISOs and SOC leads

Brief your board. Brief your team.

Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.