CVE-2025-55131: NodeJS Security leases (CVE-2025-55131, CVE-2025-55130, CVE-2025-59465, and others)
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-55131?
CVE-2025-55131 is rated as a medium severity vulnerability due to its potential to expose uninitialized memory under specific conditions.
How do I fix CVE-2025-55131?
To fix CVE-2025-55131, update Node.js to the latest version that addresses this vulnerability.
Which versions of Node.js are affected by CVE-2025-55131?
CVE-2025-55131 affects specific versions of Node.js that utilize the 'vm' module with the timeout option and may vary depending on updates.
What is the impact of CVE-2025-55131?
The impact of CVE-2025-55131 includes potential exposure of sensitive data from uninitialized memory if exploited.
Is CVE-2025-55131 exploitable in production environments?
Yes, CVE-2025-55131 could be exploitable in production environments under specific timing conditions when using affected Node.js configurations.