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

A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification

NodeJS · Node

5.3MediumCVSS 3.0
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, 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 1.38% 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: As exposure requiresRemediation target: Within 365 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

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

8 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
Alpine v3.23v3.23 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.22.13.1-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.22.13.1-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.22.13.1-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.20.19.2+dfsg-1+deb13u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.18.20.4+dfsg-1~deb12u2Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.20.18.2+dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.20.18.2+dfsg-1Debian 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-23085 · CSAF 2.0 · revision 38 · interimSUSE Product Security TeamCVE-2025-23085
151 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • nodejs10 as component of SLES-LTSS-TERADATA 15 SP2
  • nodejs12 as component of SLES-LTSS-TERADATA 15 SP2
  • nodejs14 as component of SLES-LTSS-TERADATA 15 SP2
  • 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
  • npm10 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • nodejs10 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs10-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs10-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs12 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • nodejs12-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
Summary
A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions. This vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x.
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-2025-3113

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 actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions. This vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x.

What

A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions. This vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x.

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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 could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions. This vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x.

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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 → Missing Release of Memory after Effective Lifetime → 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-401 ↗

CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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

Common Vulnerability Scoring System 3.0: 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.ALowAvailability impact: A successful attack can cause a limited 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-401
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-0156Node.js: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen preiszugeben, einen Denial-of-Service-Zustand herbeizuführen oder nicht näher spezifizierte Angriffe zu starten.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250213Security Bulletin 13 February 2025

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

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

d?id=CVE-2025-22125 Référence CVE CVE-2025-22127 https://www.cve.org/CVERecord?id=CVE-2025-22127 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22873 https://www.cve.org/CVERecord?id=CVE-2025-22873 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23085 https://www.cve.org/CVERecord?id=CVE-2025-23085 Référence CVE CVE-2025-23130 https://www.cve.org/CVERecord?id=CVE-2025-23130 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-23132 https://www.cve.org/CVERecord?id=CVE-2025-23132 Référence CVE CVE-2025-23133 https://www.cve.org/CVERecord?id=CVE-2025-23133 Référence CVE CVE-2025-23141 https://www.cve.org/CVERecord?id=CVE-2025-23141 Référence CVE CVE-2025-23155 https://www.cve.org/CVERecord?id=CVE-2025-23155 Référence CVE CVE-2025-23160 https://www.cve.org/CVERecord?id=CVE-2025-23160 Référence CVE CVE-2025-23162 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-22125 Référence CVE CVE-2025-22127 https://www.cve.org/CVERecord?id=CVE-2025-22127 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22873 https://www.cve.org/CVERecord?id=CVE-2025-22873 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23085 https://www.cve.org/CVERecord?id=CVE-2025-23085 Référence CVE CVE-2025-23130 https://www.cve.org/CVERecord?id=CVE-2025-23130 Référence CVE CVE-2025-23131 https://www.cve.org/CVERecord?id=CVE-2025-23131 Référence CVE CVE-2025-23132 https://www.cve.org/CVERecord?id=CVE-2025-23132 Référence CVE CVE-2025-23133 https://www.cve.org/CVERecord?id=CVE-2025-23133 Référence CVE CVE-2025-23141 https://www.cve.org/CVERecord?id=CVE-2025-23141 Référence CVE CVE-2025-23155 https://www.cve.org/CVERecord?id=CVE-2025-23155 Référence CVE CVE-2025-23160 https://www.cve.org/CVERecord?id=CVE-2025-23160 Référence CVE CVE-2025-23162 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-22866 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23083 https://www.cve.org/CVERecord?id=CVE-2025-23083 Référence CVE CVE-2025-23084 https://www.cve.org/CVERecord?id=CVE-2025-23084 Référence CVE CVE-2025-23085 https://www.cve.org/CVERecord?id=CVE-2025-23085 Référence CVE CVE-2025-2312 https://www.cve.org/CVERecord?id=CVE-2025-2312 Référence CVE CVE-2025-23165 https://www.cve.org/CVERecord?id=CVE-2025-23165 Référence CVE CVE-2025-23166 https://www.cve.org/CVERecord?id=CVE-2025-23166 Référence CVE CVE-2025-23167 https://www.cve.org/CVERecord?id=CVE-2025-23167 Référence CVE CVE-2025-24014 https://www.cve.org/CVERecord?id=CVE-2025-24014 Référence CVE CVE-2025-24293 https://www.cve.org/CVERecord?id=CVE-2025-24293 Référence CVE CVE-2025-24294 https://www.cve.org/CVERecord?id=CVE-2025-24294 Référence CVE CVE-2025-24813 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2025-22866 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23083 https://www.cve.org/CVERecord?id=CVE-2025-23083 Référence CVE CVE-2025-23084 https://www.cve.org/CVERecord?id=CVE-2025-23084 Référence CVE CVE-2025-23085 https://www.cve.org/CVERecord?id=CVE-2025-23085 Référence CVE CVE-2025-23165 https://www.cve.org/CVERecord?id=CVE-2025-23165 Référence CVE CVE-2025-23166 https://www.cve.org/CVERecord?id=CVE-2025-23166 Référence CVE CVE-2025-23167 https://www.cve.org/CVERecord?id=CVE-2025-23167 Référence CVE CVE-2025-24293 https://www.cve.org/CVERecord?id=CVE-2025-24293 Référence CVE CVE-2025-25186 https://www.cve.org/CVERecord?id=CVE-2025-25186 Référence CVE CVE-2025-27210 https://www.cve.org/CVERecord?id=CVE-2025-27210 Référence CVE CVE-2025-27221 https://www.cve.org/CVERecord?id=CVE-2025-27221 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-22235 Référence CVE CVE-2025-22868 https://www.cve.org/CVERecord?id=CVE-2025-22868 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-22870 https://www.cve.org/CVERecord?id=CVE-2025-22870 Référence CVE CVE-2025-22871 https://www.cve.org/CVERecord?id=CVE-2025-22871 Référence CVE CVE-2025-22872 https://www.cve.org/CVERecord?id=CVE-2025-22872 Référence CVE CVE-2025-22874 https://www.cve.org/CVERecord?id=CVE-2025-22874 Référence CVE CVE-2025-23083 https://www.cve.org/CVERecord?id=CVE-2025-23083 Référence CVE CVE-2025-23084 https://www.cve.org/CVERecord?id=CVE-2025-23084 Référence CVE CVE-2025-23085 https://www.cve.org/CVERecord?id=CVE-2025-23085 Référence CVE CVE-2025-2312 https://www.cve.org/CVERecord?id=CVE-2025-2312 Référence CVE CVE-2025-23136 https://www.cve.org/CVERecord?id=CVE-2025-23136 Référence CVE CVE-2025-23138 https://www.cve.org/CVERecord?id=CVE-2025-23138 Référence CVE CVE-2025-23140 https://www.cve.org/CVERecord?id=CVE-2025-23140 Référence CVE CVE-2025-23142 https://www.cve.org/CVERecord?id=CVE-2025-23142 Référence CVE CVE-2025-23144 https://www.cve.org/CVERecord?id=CVE-2025-23144 Référence CVE CVE-2025-23145 https://www.cve.org/CVERecord?id=CVE-2025-23145 Référence CVE CVE-2025-23146 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0724Multiples vulnérabilités dans les produits IBM

/www.ibm.com/support/pages/node/7242291 Bulletin de sécurité IBM 7242292 du 15 août 2025 https://www.ibm.com/support/pages/node/7242292 Bulletin de sécurité IBM 7242665 du 20 août 2025 https://www.ibm.com/support/pages/node/7242665 Bulletin de sécurité IBM 7242869 du 21 août 2025 https://www.ibm.com/support/pages/node/7242869 Référence CVE CVE-2018-14732 https://www.cve.org/CVERecord?id=CVE-2018-14732 Référence CVE CVE-2024-11831 https://www.cve.org/CVERecord?id=CVE-2024-11831 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2025-22150 https://www.cve.org/CVERecord?id=CVE-2025-22150 Référence CVE CVE-2025-23085 https://www.cve.org/CVERecord?id=CVE-2025-23085 Référence CVE CVE-2025-23184 https://www.cve.org/CVERecord?id=CVE-2025-23184 Référence CVE CVE-2025-26791 https://www.cve.org/CVERecord?id=CVE-2025-26791 Référence CVE CVE-2025-27516 https://www.cve.org/CVERecord?id=CVE-2025-27516 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-30359 https://www.cve.org/CVERecord?id=CVE-2025-30359 Référence CVE CVE-2025-30360 https://www.cve.org/CVERecord?id=CVE-2025-30360 Référence CVE CVE-2025-32996 https://www.cve.org/CVERecord?id=CVE-2025-32996 Référence CVE CVE-2025-32997 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0602Multiples vulnérabilités dans Oracle PeopleSoft

De multiples vulnérabilités ont été découvertes dans Oracle PeopleSoft. Elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0319Multiples vulnérabilités dans Oracle Java SE

d?id=CVE-2024-54479 Référence CVE CVE-2024-54502 https://www.cve.org/CVERecord?id=CVE-2024-54502 Référence CVE CVE-2024-54505 https://www.cve.org/CVERecord?id=CVE-2024-54505 Référence CVE CVE-2024-54508 https://www.cve.org/CVERecord?id=CVE-2024-54508 Référence CVE CVE-2024-54534 https://www.cve.org/CVERecord?id=CVE-2024-54534 Référence CVE CVE-2024-54543 https://www.cve.org/CVERecord?id=CVE-2024-54543 Référence CVE CVE-2025-21587 https://www.cve.org/CVERecord?id=CVE-2025-21587 Référence CVE CVE-2025-23083 https://www.cve.org/CVERecord?id=CVE-2025-23083 Référence CVE CVE-2025-23084 https://www.cve.org/CVERecord?id=CVE-2025-23084 Référence CVE CVE-2025-23085 https://www.cve.org/CVERecord?id=CVE-2025-23085 Référence CVE CVE-2025-24143 https://www.cve.org/CVERecord?id=CVE-2025-24143 Référence CVE CVE-2025-24150 https://www.cve.org/CVERecord?id=CVE-2025-24150 Référence CVE CVE-2025-24158 https://www.cve.org/CVERecord?id=CVE-2025-24158 Référence CVE CVE-2025-24162 https://www.cve.org/CVERecord?id=CVE-2025-24162 Référence CVE CVE-2025-30691 https://www.cve.org/CVERecord?id=CVE-2025-30691 Référence CVE CVE-2025-30698 https://www.cve.org/CVERecord?id=CVE-2025-30698 Gestion détaillée du document le 16 avril 2025 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0150Multiples vulnérabilités dans Tenable Identity Exposure

De multiples vulnérabilités ont été découvertes dans Tenable Identity Exposure. Certaines d'entre elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0102Multiples vulnérabilités dans les produits Tenable

De multiples vulnérabilités ont été découvertes dans les produits Tenable. Entre elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et un contournement de la politique de sécurité.

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

De multiples vulnérabilités ont été découvertes dans Node.js. Elles permettent à un attaquant de provoquer un déni de service à distance et un contournement de la politique de sécurité.

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
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 7 Feb 2025 · Last source change 3 Nov 2025, 21:00 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-2025-3113
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
NVD statusNVD not scheduled

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-23085 · cve.blacktree.nl