CVE-2025-551317.1HighCWE-120

CVE-2025-55131: nodejs vulnerability

nodejs · node

Vendor fix available · Affected: nodejs · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

3.5%probability of exploitation in the next 30 days

89th percentile

050100

Higher than 89% of scored CVEs

7.1HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

nodejs · nodefrom 20.19.6 up to and including 20.19.6; from 22.21.1 up to and including 22.21.1; from 24.12.0 up to and including 24.12.0; from 25.2.1 up to and including 25.2.1; from 4.0 before 4.*; from 5.0 before 5.* and 13 more

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Classic Buffer Overflow · Memory Corruption
Vendor: nodejs
Published: January 2026
Band: Possible (1 to 10%), January 2026
Bounty reports: 1 disclosed on HackerOne

Disclosed bug bounty reports about CVE-2025-55131

The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.

Timeout-based race conditions make Uint8Array/Buffer.alloc non-zerofilledNode.js · 2026 · high severityValid

CoverageNo articles yet

No CyberSIXT article names CVE-2025-55131 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

8 more references are in the CVE record.