CVE-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 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.

Published: 2026-01-20 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-55131 is rated Low Risk (30.4/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-55131

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-21 — 0.02% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-55131

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.1 3.0 HIGH
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.6 5.5 [email protected]

Weakness enumeration for CVE-2025-55131

OS Trackers for CVE-2025-55131

vendor priority summary link
alpine — CVE-2025-55131: 1 source package rows (nodejs); 4 state rows across 4 repos (3.21-main, 3.22-main, 3.23-main, edge-main); fixed 4, open 0. https://security.alpinelinux.org/vuln/CVE-2025-55131
debian unimportant CVE-2025-55131 unimportant priority: Debian including 1 source packages (nodejs), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-55131
redhat high — https://access.redhat.com/security/cve/CVE-2025-55131
suse high CVE-2025-55131 severity important: SUSE including 84 source package names (2.1.3-6.15:qemu-guest-agent-8.2.9-1.1, corepack20-20.20.0-150600.3.15.1, …), 234 product×package rows across 38 product lines (Container suse/sl-micro/6.0/kvm-os-container, Image SL-Micro, … (38 product lines)): Fixed 150, Known Not Affected 79, First Fixed 5. https://www.suse.com/security/cve/CVE-2025-55131/
ubuntu medium CVE-2025-55131 medium priority: Ubuntu including 1 source packages (nodejs), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): needs-triage 7, ignored 1, released 1. https://ubuntu.com/security/CVE-2025-55131

Affected software / configurations for CVE-2025-55131

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-55131

cvelogic Threat Intelligence