# CVE-2025-55131: Information disclosure in node

> Node.js buffer allocation flaw exposes uninitialized memory, potentially leaking secrets or corrupting data when using the vm module with timeouts.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jan 2026
- **Updated:** 15 Jul 2026
- **Also known as:** ALPINE-CVE-2025-55131, AZL-74967, AZL-74979, BELL-CVE-2025-55131, BIT-node-2025-55131, BIT-node-min-2025-55131, CLEANSTART-2026-MI22504, DEBIAN-CVE-2025-55131, GHSA-9jwr-p39p-hwg2, MINI-23mf-fgc4-96h9, MINI-2879-25p2-fj5g, MINI-3747-89qx-52wg, MINI-3c7f-4rm2-rh2g, MINI-4hr2-g5c2-6ww2, MINI-cfv7-wwhr-p5gx, MINI-p8g3-72hc-7wr7, UBUNTU-CVE-2025-55131

## What is CVE-2025-55131?

CVE-2025-55131 is a high-severity vulnerability in nodejs node, published on 20 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere), CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2025-55131?

2 open source packages ship an affected version, including node and node-min.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | All versions | 20.20.0, 22.22.0, 24.13.0, 25.3.0 |
| `node-min` | Bitnami | All versions | 20.20.0, 22.22.0, 24.13.0, 25.3.0 |

## How do I fix CVE-2025-55131?

Upgrade node to a fixed version for your release line: 20.20.0, 22.22.0, 24.13.0 or 25.3.0.

## Is CVE-2025-55131 being exploited?

There is no known exploitation of CVE-2025-55131 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-55131 and fix it if it is affected.

What it is: CVE-2025-55131 is a high-severity vulnerability in nodejs node, published on 20 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-55131 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected all versions; fixed in 20.20.0, 22.22.0, 24.13.0, 25.3.0
- node-min (Bitnami): affected all versions; fixed in 20.20.0, 22.22.0, 24.13.0, 25.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-55131/ (Markdown: https://insights.sbomify.com/CVE-2025-55131/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55131
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55131
- OSV: https://osv.dev/vulnerability/CVE-2025-55131

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-55131/
Summaries are generated and may contain mistakes; the official description above is the record.