CVE Watchtower

CVE-2025-55131nodejs node Classic Buffer Overflow

NVDCVSS scored by 0b0ca135-0b70-47e7-9f44-1890c2a1c46c

Vulnerability Summary

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.
Severity Level
HIGH(7.1)
Published Date
Jan 20, 2026
Last Modified
Jul 15, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
3.26%Probability
Root Weakness (CWE)
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
See the MITRE CWE entry for the full definition of this weakness.
CVSS v3.1 Base Metrics — Score 7.1 (HIGH)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityLow

Affected & Patched Versions

Affected Versions
  • nodejs node >= 20.19.6 and <= 20.19.6
  • nodejs node >= 22.21.1 and <= 22.21.1
  • nodejs node >= 24.12.0 and <= 24.12.0
  • nodejs node >= 25.2.1 and <= 25.2.1
  • nodejs node >= 4.0 and < 4.*
  • nodejs node >= 5.0 and < 5.*
  • nodejs node >= 6.0 and < 6.*
  • nodejs node >= 7.0 and < 7.*
  • nodejs node >= 8.0 and < 8.*
  • nodejs node >= 9.0 and < 9.*
  • nodejs node >= 10.0 and < 10.*
  • nodejs node >= 11.0 and < 11.*
  • nodejs node >= 12.0 and < 12.*
  • nodejs node >= 13.0 and < 13.*
  • nodejs node >= 14.0 and < 14.*
  • nodejs node >= 15.0 and < 15.*
  • nodejs node >= 16.0 and < 16.*
  • nodejs node >= 17.0 and < 17.*
  • nodejs node >= 18.0 and < 18.*
Patched Versions
  • nodejs node 20.19.6
  • nodejs node 22.21.1
  • nodejs node 24.12.0
  • nodejs node 25.2.1
  • nodejs node 4.*
  • nodejs node 5.*
  • nodejs node 6.*
  • nodejs node 7.*
  • nodejs node 8.*
  • nodejs node 9.*
  • nodejs node 10.*
  • nodejs node 11.*
  • nodejs node 12.*
  • nodejs node 13.*
  • nodejs node 14.*
  • nodejs node 15.*
  • nodejs node 16.*
  • nodejs node 17.*
  • nodejs node 18.*

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run nodejs node and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Jan 20, 2026Published
  • Jul 15, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new nodejs node CVEsYou are reading CVE-2025-55131. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 22, 2026 14:11 UTC