Skip to main content
CVE-2025-55131VulnerabilityPublished Updated

CVE-2025-55131: nodejs node · Buffer Overflow

Affects nodejs nodeSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.4% chance of exploitation in 30 days – higher than 88% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-25.

What to do

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • >=20.19.6 <=20.19.6
  • >=22.21.1 <=22.21.1
  • >=24.12.0 <=24.12.0
  • >=25.2.1 <=25.2.1
  • =4.0
  • =5.0
  • =6.0
  • =7.0
  • =8.0
  • =9.0
  • =10.0
  • =11.0
  • =12.0
  • =13.0
  • =14.0
  • =15.0
  • =16.0
  • =17.0
  • =18.0
Fixed in–

AI-suggested

Red Hat has released security updates that fix this vulnerability in their Node.js packages. Users of affected Red Hat Enterprise Linux versions should apply the relevant updates as described in the Red Hat advisories (e.g., RHSA-2026:2899). Since this is not a cloud service, remediation requires applying these patches. Patch status is confirmed by Red Hat advisories. No indication of 'no action required' or 'already mitigated' was found, so applying the official patches is recommended.

Description

A flaw in Node.js's buffer allocation logic can expose uninitialized memory when allocations are interrupted, when using the `vm` module with the timeout option. Under specific timing conditions, buffers allocated with `Buffer.alloc` and other `TypedArray` instances like `Uint8Array` may contain leftover data from previous operations, allowing in-process secrets like tokens or passwords to leak or causing data corruption. While exploitation typically requires precise timing or in-process code execution, it can become remotely exploitable when untrusted input influences workload and timeouts, leading to potential confidentiality and integrity impact.

References

Community reviews

Loading reviews…