CVE-2025-23165VulnerabilityPublished 3 Jun 2025Updated 11 Oct 2026

SUSE · security update for nodejs

Affects SUSESource GCVE Database

Mentioned vulnerabilities

CVE-2025-23166

Not known to be exploited : upgrade to 22.16.0 soon.

Data as of 26 Oct 2026, 06:26 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 22.16.0

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade SUSE to 22.16.0.

Affected software

Product	Affected	Fixed in
SUSE Product Security Team SUSE	Affected >=22.0.0 <22.16.0	Fixed in 22.16.0

AI-suggested

Red Hat has released an official security update that rebases Node.js 22 to the latest release, which addresses this vulnerability. Users should apply the update for the nodejs:22 module on Red Hat Enterprise Linux 8 as detailed in the Red Hat advisory RHSA-2025:8506. No additional mitigation steps are indicated by the vendor.

Description

A security vulnerability identified as CVE-2025-23166 affects Node.js 22 on Red Hat Enterprise Linux 8. The flaw allows a remote crash via the SignTraits::DeriveBits() function and is rated as having a high severity impact by Red Hat Product Security. The issue affects multiple architectures including x86_64, s390x, ppc64le, and aarch64. Red Hat has issued a security update rebasing Node.js 22 to the latest release to address this vulnerability. No known exploits have been reported in the wild at this time.

Impact

The vulnerability allows a remote attacker to cause a crash in Node.js 22, potentially leading to denial of service conditions on affected systems. The severity is considered high by Red Hat Product Security, indicating a significant impact on availability. There are no reports of active exploitation in the wild.

Summary

CVE-2025-23166 is a vulnerability in Node.js 22 on Red Hat Enterprise Linux 8 that allows remote crashing of the application through the SignTraits::DeriveBits() function. This vulnerability is rated as important/high severity by Red Hat Product Security. The update rebases Node.js 22 to the latest release to mitigate this issue. The advisory covers multiple hardware architectures and is applicable to the nodejs:22 module. No CVSS score is provided, and no active exploitation has been observed.

CWE-401Missing Release of Memory after Effective Lifetime (opens in a new tab)
Variant weaknessLikelihood of exploit: Medium
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
Implementation · Libraries or Frameworks
Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Architecture and Design · Build and Compilation
Consider using the Boehm-Demers-Weiser garbage collector (bdwgc), which can help avoid leaks.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-248Uncaught Exception (opens in a new tab)
Base weaknessOWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
An exception is thrown from a function, but it is not caught.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Oct 2026, 22:14 UTC

WeaknessesCWE-401, CWE-248

Technical details

References

Community reviews

Related threats