Skip to main content
No exploitation reportedFix available

CVE-2025-55131

No exploitation reported by the sources we read.

  • Published2026-01-20
  • Fixed in25.3.0 · 24.13.0 · 22.22.0 · 20.20.0
  • WeaknessCWE-120 · CWE-497

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-01-2021:16CVE publishedNVD

Versions per branch

OSV
node
BranchAffectedFixed in
25.x≥ 25.0.0, < 25.3.025.3.0
24.13≥ 23.0.0, < 24.13.024.13.0
22.22≥ 21.0.0, < 22.22.022.22.0
20.20< 20.20.020.20.0
node-min
BranchAffectedFixed in
25.x≥ 25.0.0, < 25.3.025.3.0
24.13≥ 23.0.0, < 24.13.024.13.0
22.22≥ 21.0.0, < 22.22.022.22.0
20.20< 20.20.020.20.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As hackerone, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • nodejs nodeother versions: not affected
    Affected
    • ≥ 20.19.6, ≤ 20.19.6no fix statedsemver
    • ≥ 22.21.1, ≤ 22.21.1no fix statedsemver
    • ≥ 24.12.0, ≤ 24.12.0no fix statedsemver
    • ≥ 25.2.1, ≤ 25.2.1no fix statedsemver
    • ≥ 4.0, < 4.*no fix statedsemver
    • ≥ 5.0, < 5.*no fix statedsemver
    • ≥ 6.0, < 6.*no fix statedsemver
    • ≥ 7.0, < 7.*no fix statedsemver

    11 more version lines in the CVE record.

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-01-20

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • apache-supersetCleanStartall versions · fixed in 5.0.0-r10
  • nodejsUbuntu:Pro:22.04:LTSall versions · no fixed version listed
  • nodejsUbuntu:Pro:20.04:LTSall versions · no fixed version listed
  • nodejsUbuntu:Pro:18.04:LTSall versions · no fixed version listed
  • nodejsUbuntu:Pro:16.04:LTSall versions · no fixed version listed
  • nodejsUbuntu:Pro:14.04:LTSall versions · no fixed version listed
  • nodejsUbuntu:26.04:LTSall versions · no fixed version listed
  • nodejsUbuntu:25.10all versions · no fixed version listed

183 more package ranges on OSV.dev

Vendor advisories

  • CVE-2025-55131 Red Hat Product Security542 products fixed

    nodejs: Nodejs uninitialized memory exposure

  • RHSA-2026:7657 Red Hat Product Security17 products fixed

    Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

  • RHSA-2026:7387 Red Hat Product Security17 products fixed

    Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

  • RHSA-2026:7386 Red Hat Product Security17 products fixed

    Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

  • RHSA-2026:7378 Red Hat Product Security17 products fixed

    Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

  • RHSA-2026:6431 Red Hat Product Security17 products fixed

    Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update

13 more advisories

Full record on NVD

Fix

  1. Update node to 25.3.0 · 24.13.0 · 22.22.0 · 20.20.0
  2. Vendor fix Red Hat Product Security RHSA-2026:7657 · 17 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
  3. Vendor fix Red Hat Product Security RHSA-2026:2899 · 38 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  4. Workaround from the vendor Red Hat Product Security RHSA-2026:7657 · 19 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2026-01-22
  • CNACVSS 3.17.1known since 2026-10-23
  • CNACVSS 3.07.1known since 2026-10-23
  • CISA-ADPweakness (CWE)CWE-1202026-01-21
  • CNAweakness (CWE)CWE-497known since 2026-10-23
  • FIRST EPSSEPSS score3.5 %2026-11-08
  • OSVaffected packages—
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
Published
2026-01-20
Last Modified
2026-07-15
NVD status
Deferred
GitHub Advisory
GHSA-9jwr-p39p-hwg2

Frequently asked questions

What is 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.

Is CVE-2025-55131 actively exploited?

Active exploitation of CVE-2025-55131 has not been confirmed. Its EPSS score was 3.5% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-55131?

CVE-2025-55131 has a CVSS v3 base score of 7.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L.

Running Node.js? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record