CVE-2025-55131
published 2026-01-20CVE-2025-55131: 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…
PriorityP351high7.1CVSS 3.1
AVNACHPRLUINSUCHIHAL
EPSS
3.49%
87.9th percentile
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
22 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | nodejs | < nodejs 22.22.0+dfsg+~cs22.19.6-1 (forky) | nodejs 22.22.0+dfsg+~cs22.19.6-1 (forky) |
| nodejs | node | >= 10.0 < 10.* | 10.* |
| nodejs | node | >= 11.0 < 11.* | 11.* |
| nodejs | node | >= 12.0 < 12.* | 12.* |
| nodejs | node | >= 13.0 < 13.* | 13.* |
| nodejs | node | >= 14.0 < 14.* | 14.* |
| nodejs | node | >= 15.0 < 15.* | 15.* |
| nodejs | node | >= 16.0 < 16.* | 16.* |
| nodejs | node | >= 17.0 < 17.* | 17.* |
| nodejs | node | >= 18.0 < 18.* | 18.* |
| nodejs | node | 20.19.6 – 20.19.6 | — |
| nodejs | node | 22.21.1 – 22.21.1 | — |
| nodejs | node | 24.12.0 – 24.12.0 | — |
| nodejs | node | 25.2.1 – 25.2.1 | — |
| nodejs | node | >= 4.0 < 4.* | 4.* |
| nodejs | node | >= 5.0 < 5.* | 5.* |
| nodejs | node | >= 6.0 < 6.* | 6.* |
| nodejs | node | >= 7.0 < 7.* | 7.* |
| nodejs | node | >= 8.0 < 8.* | 8.* |
| nodejs | node | >= 9.0 < 9.* | 9.* |
| nodejs | nodejs | >= 0 < 20.19.2+dfsg-1+deb13u1 | 20.19.2+dfsg-1+deb13u1 |
| nodejs | nodejs | >= 0 < 22.22.0+dfsg+~cs22.19.6-1 | 22.22.0+dfsg+~cs22.19.6-1 |
CVSS provenance
nvdv3.17.1HIGHCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
nvdv3.07.1HIGHCVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
osv7.1HIGH
vendor_debian7.1HIGH
vendor_redhat7.1HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
nodejs: Nodejs uninitialized memory exposure
vendor_redhat·2026-01-20·CVSS 7.1
CVE-2025-55131 [HIGH] CWE-497 nodejs: Nodejs uninitialized memory exposure
nodejs: Nodejs uninitialized memory exposure
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.
A memory exposure flaw has been discovered in Node.js. A flaw in Node.js's buffer allocation lo
Debian
CVE-2025-55131: nodejs - A flaw in Node.js's buffer allocation logic can expose uninitialized memory when...
vendor_debian·2025·CVSS 7.1
CVE-2025-55131 [HIGH] CVE-2025-55131: nodejs - A flaw in Node.js's buffer allocation logic can expose uninitialized memory when...
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.
Scope: local
bookworm: open
bullseye: open
forky: resolved (fixed in 22.22.0+dfsg+~cs22.19.6-1)
sid: resolved (fixed in 22.22.0+dfsg+~cs22.19.
GHSA
GHSA-9jwr-p39p-hwg2: A flaw in Node
ghsa_unreviewed·2026-01-20
CVE-2025-55131 [HIGH] CWE-120 GHSA-9jwr-p39p-hwg2: A flaw in Node
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.
OSV
CVE-2025-55131: A flaw in Node
osv·2026-01-20·CVSS 7.1
CVE-2025-55131 [HIGH] CVE-2025-55131: A flaw in Node
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.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2025-55131 nodejs18: Nodejs uninitialized memory exposure [fedora-42]
bugzilla·2026-01-21·CVSS 7.1
CVE-2025-55131 [HIGH] CVE-2025-55131 nodejs18: Nodejs uninitialized memory exposure [fedora-42]
CVE-2025-55131 nodejs18: Nodejs uninitialized memory exposure [fedora-42]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Discussion:
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version'
to
Bugzilla
CVE-2025-55131 nodejs: Nodejs uninitialized memory exposure
bugzilla·2026-01-20·CVSS 7.1
CVE-2025-55131 [HIGH] CVE-2025-55131 nodejs: Nodejs uninitialized memory exposure
CVE-2025-55131 nodejs: Nodejs uninitialized memory exposure
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.
Discussion:
This issue has been addressed in the following products:
Red Hat E
Wiz
CVE-2025-55131 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz·CVSS 7.1
CVE-2025-55131 [HIGH] CVE-2025-55131 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2025-55131 :
npm vulnerability analysis and mitigation
vm
Buffer.alloc
TypedArray
Uint8Array
Source : NVD
## 7.1
Score
Published January 20, 2026
Severity HIGH
CNA Score 7.1
Affected Technologies
npm
Node.js
Has Public Exploit No
Has CISA KEV Exploit No
CISA KEV Release Date N/A
CISA KEV Due Date N/A
Exploitation Probability Percentile (EPSS) 9.8
Exploitation Probability (EPSS) N/A
Affected packages and libraries
nodejs20-libs-debuginfo
nodejs22-libs-debuginfo
Sources
NVD
AlmaLinux 8 Severity HIGH Has Fix Added at: Feb 15, 2026
AlmaLinux 9 Severity HIGH Has Fix Added at: Feb 19, 2026
Alpine 3.21 Severity HIGH Has Fix Added at: Apr 06, 2026
Alpine 3.22 Severity HIGH Has Fix Added at: Jan 23, 2026
Alpine 3.23, edge Severity HIGH Has Fix Added at: Jan 18
https://nodejs.org/en/blog/vulnerability/december-2025-security-releaseshttps://access.redhat.com/errata/RHSA-2026:1842https://access.redhat.com/errata/RHSA-2026:1843https://access.redhat.com/errata/RHSA-2026:2420https://access.redhat.com/errata/RHSA-2026:2421https://access.redhat.com/errata/RHSA-2026:2422https://access.redhat.com/errata/RHSA-2026:2767https://access.redhat.com/errata/RHSA-2026:2768https://access.redhat.com/errata/RHSA-2026:2781https://access.redhat.com/errata/RHSA-2026:2782https://access.redhat.com/errata/RHSA-2026:2783https://access.redhat.com/errata/RHSA-2026:2864https://access.redhat.com/errata/RHSA-2026:2899https://access.redhat.com/errata/RHSA-2026:6402https://access.redhat.com/errata/RHSA-2026:6431https://access.redhat.com/errata/RHSA-2026:7386https://access.redhat.com/errata/RHSA-2026:7387https://access.redhat.com/security/cve/CVE-2025-55131https://bugzilla.redhat.com/show_bug.cgi?id=2431350https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-55131.json
2026-01-20
Published