A memory leak in Node.js’s OpenSSL integration occurs when converting X.509 certificate fields to UTF-8 without freeing the allocated buffer. (CVE-2025-59464)
A memory leak vulnerability exists in Node.js's OpenSSL integration when converting X.509 certificate fields to UTF-8. This occurs because the allocated buffer is not freed during the conversion process. Applications invoking socket.getPeerCertificate(true) leak memory for each certificate field, which can be exploited by remote clients to cause steady memory growth through repeated TLS connections. Over time, this can lead to resource exhaustion and denial of service. The issue affects Node.js versions from 24.0.0 up to but not including 24.12.0. A patch is available to address this vulnerability.
AI Analysis
Technical Summary
CVE-2025-59464 describes a memory leak in Node.js's OpenSSL integration triggered during the conversion of X.509 certificate fields to UTF-8. Specifically, when applications call socket.getPeerCertificate(true), the allocated buffers for certificate fields are not freed, causing memory to leak. This leak can be exploited remotely by clients establishing repeated TLS connections, leading to gradual memory consumption growth and potential denial of service due to resource exhaustion. The vulnerability affects Node.js versions >=24.0.0 and <24.12.0. A patch is available to fix this issue.
Potential Impact
Remote clients can cause steady memory growth on affected Node.js servers by repeatedly establishing TLS connections that trigger the memory leak. This can lead to resource exhaustion and denial of service conditions on the server. There are no known exploits in the wild at this time.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade Node.js to version 24.12.0 or later to remediate the memory leak. No additional mitigation steps are indicated.
A memory leak in Node.js’s OpenSSL integration occurs when converting X.509 certificate fields to UTF-8 without freeing the allocated buffer. (CVE-2025-59464)
Description
A memory leak vulnerability exists in Node.js's OpenSSL integration when converting X.509 certificate fields to UTF-8. This occurs because the allocated buffer is not freed during the conversion process. Applications invoking socket.getPeerCertificate(true) leak memory for each certificate field, which can be exploited by remote clients to cause steady memory growth through repeated TLS connections. Over time, this can lead to resource exhaustion and denial of service. The issue affects Node.js versions from 24.0.0 up to but not including 24.12.0. A patch is available to address this vulnerability.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-59464 describes a memory leak in Node.js's OpenSSL integration triggered during the conversion of X.509 certificate fields to UTF-8. Specifically, when applications call socket.getPeerCertificate(true), the allocated buffers for certificate fields are not freed, causing memory to leak. This leak can be exploited remotely by clients establishing repeated TLS connections, leading to gradual memory consumption growth and potential denial of service due to resource exhaustion. The vulnerability affects Node.js versions >=24.0.0 and <24.12.0. A patch is available to fix this issue.
Potential Impact
Remote clients can cause steady memory growth on affected Node.js servers by repeatedly establishing TLS connections that trigger the memory leak. This can lead to resource exhaustion and denial of service conditions on the server. There are no known exploits in the wild at this time.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade Node.js to version 24.12.0 or later to remediate the memory leak. No additional mitigation steps are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-node-2025-59464
- Osv Schema Version
- 1.6.2
- Aliases
- ["CVE-2025-59464"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- High
Threat ID: 6aa005faacd9273b49ab68a7
Added to database: 09/08/2026, 12:56:26 UTC
Last enriched: 09/08/2026, 13:36:37 UTC
Last updated: 09/10/2026, 19:36:51 UTC
Views: 32
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.