CVE-2025-59464: nodejs vulnerability
nodejs · node
Vendor fix available · Affected: nodejs · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 19% of scored CVEs
DescriptionCVE.org
A memory leak in Node.js’s OpenSSL integration occurs when converting `X.509` certificate fields to UTF-8 without freeing the allocated buffer. When applications call `socket.getPeerCertificate(true)`, each certificate field leaks memory, allowing remote clients to trigger steady memory growth through repeated TLS connections. Over time this can lead to resource exhaustion and denial of service.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- nodejs · nodefrom 24.12.0 before 24.12.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- nodejs
- Published
- January 2026
- Bounty reports
- 1 disclosed on HackerOne
Disclosed bug bounty reports about CVE-2025-59464
The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.
- Memory leak that enables remote Denial of Service against applications processing TLS client certificatesNode.js · 2026 · medium severityValid
CoverageNo articles yet
No CyberSIXT article names CVE-2025-59464 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.