Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 21 Jan 2026 21:15:00 +0900
| Type | Values Removed | Values Added |
|---|---|---|
| Title | nodejs: Nodejs memory leak | |
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Wed, 21 Jan 2026 20:30:00 +0900
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nodejs
Nodejs nodejs |
|
| Vendors & Products |
Nodejs
Nodejs nodejs |
Wed, 21 Jan 2026 05:45:00 +0900
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| References |
| |
| Metrics |
cvssV3_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2026-01-20T20:41:55.599Z
Reserved: 2025-09-16T15:00:07.875Z
Link: CVE-2025-59464
No data.
Status : Received
Published: 2026-01-20T21:16:03.900
Modified: 2026-01-20T21:16:03.900
Link: CVE-2025-59464
OpenCVE Enrichment
Updated: 2026-01-21T20:18:42Z