BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2025-59464High confidence

When applications call `socket.getPeerCertificate(true)`, each certificate field leaks memory, allowing remote clients to trigger steady memory growth through repeated TLS connections

nodejs · node

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.27% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs nodejs node and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcenodejsNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenodejsNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenodejsNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenodejsNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivenodejsUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-59464 · CSAF 2.0 · revision 19 · interimSUSE Product Security TeamCVE-2025-59464
322 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • nodejs18 as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • nodejs18-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • nodejs18-docs as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • npm18 as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • nodejs10 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs10-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs10-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs8 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs8-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs8-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • npm10 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • npm8 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-3340

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.

What

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.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

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.

Why

The product does not properly control the allocation and maintenance of a limited resource.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Uncontrolled Resource Consumption → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-400 ↗

CWE-400: Uncontrolled Resource Consumption. The product does not properly control the allocation and maintenance of a limited resource.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-400
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0098Node.js: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um beliebigen Code auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren und vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260121Security Bulletin 21 Jan 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 21 Jan 2026, published on 21 January 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0627Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2025-55131 Référence CVE CVE-2025-55132 https://www.cve.org/CVERecord?id=CVE-2025-55132 Référence CVE CVE-2025-55159 https://www.cve.org/CVERecord?id=CVE-2025-55159 Référence CVE CVE-2025-58057 https://www.cve.org/CVERecord?id=CVE-2025-58057 Référence CVE CVE-2025-58060 https://www.cve.org/CVERecord?id=CVE-2025-58060 Référence CVE CVE-2025-58187 https://www.cve.org/CVERecord?id=CVE-2025-58187 Référence CVE CVE-2025-58188 https://www.cve.org/CVERecord?id=CVE-2025-58188 Référence CVE CVE-2025-58190 https://www.cve.org/CVERecord?id=CVE-2025-58190 Référence CVE CVE-2025-58436 https://www.cve.org/CVERecord?id=CVE-2025-58436 Référence CVE CVE-2025-59464 https://www.cve.org/CVERecord?id=CVE-2025-59464 Référence CVE CVE-2025-59465 https://www.cve.org/CVERecord?id=CVE-2025-59465 Référence CVE CVE-2025-59466 https://www.cve.org/CVERecord?id=CVE-2025-59466 Référence CVE CVE-2025-6069 https://www.cve.org/CVERecord?id=CVE-2025-6069 Référence CVE CVE-2025-6075 https://www.cve.org/CVERecord?id=CVE-2025-6075 Référence CVE CVE-2025-61723 https://www.cve.org/CVERecord?id=CVE-2025-61723 Référence CVE CVE-2025-61725 https://www.cve.org/CVERecord?id=CVE-2025-61725 Référence CVE CVE-2025-61726 https://www.cve.org/CVERecord?id=CVE-2025-61726 Référence CVE CVE-2025-61728 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2025-58181 Référence CVE CVE-2025-58183 https://www.cve.org/CVERecord?id=CVE-2025-58183 Référence CVE CVE-2025-58185 https://www.cve.org/CVERecord?id=CVE-2025-58185 Référence CVE CVE-2025-58186 https://www.cve.org/CVERecord?id=CVE-2025-58186 Référence CVE CVE-2025-58187 https://www.cve.org/CVERecord?id=CVE-2025-58187 Référence CVE CVE-2025-58188 https://www.cve.org/CVERecord?id=CVE-2025-58188 Référence CVE CVE-2025-58189 https://www.cve.org/CVERecord?id=CVE-2025-58189 Référence CVE CVE-2025-5918 https://www.cve.org/CVERecord?id=CVE-2025-5918 Référence CVE CVE-2025-59375 https://www.cve.org/CVERecord?id=CVE-2025-59375 Référence CVE CVE-2025-59464 https://www.cve.org/CVERecord?id=CVE-2025-59464 Référence CVE CVE-2025-59465 https://www.cve.org/CVERecord?id=CVE-2025-59465 Référence CVE CVE-2025-59466 https://www.cve.org/CVERecord?id=CVE-2025-59466 Référence CVE CVE-2025-59691 https://www.cve.org/CVERecord?id=CVE-2025-59691 Référence CVE CVE-2025-59692 https://www.cve.org/CVERecord?id=CVE-2025-59692 Référence CVE CVE-2025-59830 https://www.cve.org/CVERecord?id=CVE-2025-59830 Référence CVE CVE-2025-6069 https://www.cve.org/CVERecord?id=CVE-2025-6069 Référence CVE CVE-2025-6075 https://www.cve.org/CVERecord?id=CVE-2025-6075 Référence CVE CVE-2025-60753 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2025-58181 Référence CVE CVE-2025-58183 https://www.cve.org/CVERecord?id=CVE-2025-58183 Référence CVE CVE-2025-58185 https://www.cve.org/CVERecord?id=CVE-2025-58185 Référence CVE CVE-2025-58186 https://www.cve.org/CVERecord?id=CVE-2025-58186 Référence CVE CVE-2025-58187 https://www.cve.org/CVERecord?id=CVE-2025-58187 Référence CVE CVE-2025-58188 https://www.cve.org/CVERecord?id=CVE-2025-58188 Référence CVE CVE-2025-58189 https://www.cve.org/CVERecord?id=CVE-2025-58189 Référence CVE CVE-2025-5918 https://www.cve.org/CVERecord?id=CVE-2025-5918 Référence CVE CVE-2025-59375 https://www.cve.org/CVERecord?id=CVE-2025-59375 Référence CVE CVE-2025-59464 https://www.cve.org/CVERecord?id=CVE-2025-59464 Référence CVE CVE-2025-59465 https://www.cve.org/CVERecord?id=CVE-2025-59465 Référence CVE CVE-2025-59466 https://www.cve.org/CVERecord?id=CVE-2025-59466 Référence CVE CVE-2025-59691 https://www.cve.org/CVERecord?id=CVE-2025-59691 Référence CVE CVE-2025-59692 https://www.cve.org/CVERecord?id=CVE-2025-59692 Référence CVE CVE-2025-60753 https://www.cve.org/CVERecord?id=CVE-2025-60753 Référence CVE CVE-2025-60876 https://www.cve.org/CVERecord?id=CVE-2025-60876 Référence CVE CVE-2025-6141 https://www.cve.org/CVERecord?id=CVE-2025-6141 Référence CVE CVE-2025-61661 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2025-58185 Référence CVE CVE-2025-58186 https://www.cve.org/CVERecord?id=CVE-2025-58186 Référence CVE CVE-2025-58187 https://www.cve.org/CVERecord?id=CVE-2025-58187 Référence CVE CVE-2025-58188 https://www.cve.org/CVERecord?id=CVE-2025-58188 Référence CVE CVE-2025-58189 https://www.cve.org/CVERecord?id=CVE-2025-58189 Référence CVE CVE-2025-58767 https://www.cve.org/CVERecord?id=CVE-2025-58767 Référence CVE CVE-2025-5889 https://www.cve.org/CVERecord?id=CVE-2025-5889 Référence CVE CVE-2025-5914 https://www.cve.org/CVERecord?id=CVE-2025-5914 Référence CVE CVE-2025-59375 https://www.cve.org/CVERecord?id=CVE-2025-59375 Référence CVE CVE-2025-59464 https://www.cve.org/CVERecord?id=CVE-2025-59464 Référence CVE CVE-2025-59775 https://www.cve.org/CVERecord?id=CVE-2025-59775 Référence CVE CVE-2025-6020 https://www.cve.org/CVERecord?id=CVE-2025-6020 Référence CVE CVE-2025-6021 https://www.cve.org/CVERecord?id=CVE-2025-6021 Référence CVE CVE-2025-6052 https://www.cve.org/CVERecord?id=CVE-2025-6052 Référence CVE CVE-2025-6069 https://www.cve.org/CVERecord?id=CVE-2025-6069 Référence CVE CVE-2025-6075 https://www.cve.org/CVERecord?id=CVE-2025-6075 Référence CVE CVE-2025-60876 https://www.cve.org/CVERecord?id=CVE-2025-60876 Référence CVE CVE-2025-61594 https://www.cve.org/CVERecord?id=CVE-2025-6

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0039Multiples vulnérabilités dans Node.js

De multiples vulnérabilités ont été découvertes dans Node.js. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une élévation de privilèges et un déni de service à distance.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-002195Node.js FoundationのNode.jsにおけるリソースの枯渇に関する脆弱性

Node.jsのOpenSSL統合において、`X.509`証明書フィールドをUTF-8に変換する際に割り当てられたバッファが解放されず、メモリリークが発生します。アプリケーションが`socket.getPeerCertificate(true)`を呼び出すと、各証明書フィールドでメモリがリークし、リモートクライアントが繰り返しTLS接続を行うことでメモリが継続的に増加します。これにより、時間の経過とともにリソースが枯渇し、サービス拒否(DoS)を引き起こす可能性があります。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
node: 24.12.0 < 24.12.0
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 20 Jan 2026 · Last source change 21 Jan 2026, 20:41 UTC · CWE-400 · Uncontrolled Resource Consumption

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-3340
Product sourceCNA
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    SUSE Product Security Team ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-59464 · cve.blacktree.nl