Missing Release of Memory after Effective Lifetime Affecting node package, versions [24.0.0,24.12.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Missing Release of Memory after Effective Lifetime vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-UPSTREAM-NODE-14988767
- published16 Jan 2026
- disclosed13 Jan 2026
- creditgiant_anteater
Introduced: 13 Jan 2026
CVE-2025-59464 (opens in a new tab)How to fix?
Upgrade node to version 24.12.0 or higher.
Overview
node is a JavaScript runtime built on Chrome's V8 JavaScript engine.
Affected versions of this package are vulnerable to Missing Release of Memory after Effective Lifetime in the OpenSSL integration. When the application calls socket.getPeerCertificate(true) (passing true to retrieve the full certificate details), Node.js converts X.509 certificate fields to UTF-8 but fails to free the allocated buffers. A remote attacker can establish repeated TLS connections to the server. If the server application requests the peer certificate with details, each connection leaks a small amount of memory, potentially leading to steady memory growth over time and eventual resource exhaustion (OOM), crashing the service.
Note:
This is only exploitable if the application calls getPeerCertificate(true).