Remote service interruption via certificate-field memory leak
Published Jan 20, 2026 · Updated Jan 20, 2026
Memory leakage in Node.js 24.x before 24.12.0 allows remote attackers to exhaust TLS service memory through repeated connections. The OpenSSL certificate-field conversion path allocates UTF-8 buffers without freeing them when socket.getPeerCertificate(true) requests detailed X.509 data. Exposure requires an application to invoke that detailed peer-certificate path; repeated TLS clients then cause steady memory growth and eventual service interruption.
Summary
What happened
Memory leakage in Node.js 24.x before 24.12.0 allows remote attackers to exhaust TLS service memory through repeated connections. The OpenSSL certificate-field conversion path allocates UTF-8 buffers without freeing them when socket.getPeerCertificate(true) requests detailed X.509 data. Exposure requires an application to invoke that detailed peer-certificate path; repeated TLS clients then cause steady memory growth and eventual service interruption.
The record
- CVE
- CVE-2025-59464
- Published
- Jan 20, 2026
- Updated
- Jan 20, 2026
- Vendor
- Node.js
- Product
- Node.js
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 20, 2026CVE publishedPublication date reported by the CVE source.
- Jan 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=24.12.0 <24.12.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo