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 wit
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.4% (FIRST EPSS); higher than 89% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: nodejs node 10.*, 11.*, 12.*.
Low priority for now. Upgrade to nodejs node 10.*, 11.*, 12.* or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2026-00546
- ALSA-2026:1842
- ALSA-2026:1843
- ALSA-2026:2420
- ALSA-2026:2421
- ALSA-2026:2422
- ALSA-2026:2781
- ALSA-2026:2782
- ALSA-2026:2783
- DSA-6166-1
- openSUSE-SU-2026:10062-1
- openSUSE-SU-2026:10074-1
- openSUSE-SU-2026:11110-1
- openSUSE-SU-2026:20236-1
- RHSA-2026:1842
- RHSA-2026:1843
- RHSA-2026:2420
- RHSA-2026:2421
- RHSA-2026:2422
- RHSA-2026:2767
- Published
- Jan 20, 2026
- Updated
- Jul 15, 2026
- EPSS
- 3.4% · 89th percentile
- CWE
- CWE-120
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · hackerone
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| enterprise linux | 10.1 | cpe:2.3:redhat:enterprise_linux:10.1 |
| enterprise linux eus | 10.0 | cpe:2.3:redhat:enterprise_linux_eus:10.0 |
| enterprise linux | 8 | cpe:2.3:redhat:enterprise_linux:8 |
| enterprise linux | 9 | cpe:2.3:redhat:enterprise_linux:9 |
| rhel eus | 9.4 | cpe:2.3:redhat:rhel_eus:9.4 |
| rhel eus | 9.6 | cpe:2.3:redhat:rhel_eus:9.6 |
| hummingbird | 1 | cpe:2.3:redhat:hummingbird:1 |
Using node? Add it to your stack and be the first to know about CVEs like this one. (Node.js)
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.
nodejs node
- 20.19.6 and later · up to and including 20.19.6affected · semver
- 22.21.1 and later · up to and including 22.21.1affected · semver
- 24.12.0 and later · up to and including 24.12.0affected · semver
- 25.2.1 and later · up to and including 25.2.1affected · semver
- 4.0 and later · before 4.*affected · semver
- 5.0 and later · before 5.*affected · semver
- 6.0 and later · before 6.*affected · semver
- 7.0 and later · before 7.*affected · semver
- 8.0 and later · before 8.*affected · semver
- 9.0 and later · before 9.*affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | nodejs-docs | before 1:22.22.0-3.el10_1 | 1:22.22.0-3.el10_1 |
| AlmaLinux:10 | nodejs24-docs | before 1:24.13.0-1.el10_1 | 1:24.13.0-1.el10_1 |
| AlmaLinux:10 | nodejs24-npm | before 1:11.6.2-1.24.13.0.1.el10_1 | 1:11.6.2-1.24.13.0.1.el10_1 |
| AlmaLinux:8 | nodejs | before 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 | 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 |
| AlmaLinux:8 | nodejs | before 1:22.22.0-1.module_el8.10.0+4112+db1af44b | 1:22.22.0-1.module_el8.10.0+4112+db1af44b |
| AlmaLinux:8 | nodejs-devel | before 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 | 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 |
| AlmaLinux:8 | nodejs-devel | before 1:22.22.0-1.module_el8.10.0+4112+db1af44b | 1:22.22.0-1.module_el8.10.0+4112+db1af44b |
| AlmaLinux:8 | nodejs-docs | before 1:22.22.0-1.module_el8.10.0+4112+db1af44b | 1:22.22.0-1.module_el8.10.0+4112+db1af44b |
| AlmaLinux:8 | nodejs-docs | before 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 | 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 |
| AlmaLinux:8 | nodejs-full-i18n | before 1:22.22.0-1.module_el8.10.0+4112+db1af44b | 1:22.22.0-1.module_el8.10.0+4112+db1af44b |
| AlmaLinux:8 | nodejs-full-i18n | before 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 | 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 |
| AlmaLinux:8 | nodejs-libs | before 1:22.22.0-1.module_el8.10.0+4112+db1af44b | 1:22.22.0-1.module_el8.10.0+4112+db1af44b |
| AlmaLinux:8 | nodejs-libs | before 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 | 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 |
| AlmaLinux:8 | nodejs-nodemon | before 3.0.1-1.module_el8.10.0+4006+3c416519 | 3.0.1-1.module_el8.10.0+4006+3c416519 |
| AlmaLinux:8 | nodejs-nodemon | before 3.0.1-1.module_el8.10.0+3982+85c136aa | 3.0.1-1.module_el8.10.0+3982+85c136aa |
| AlmaLinux:8 | nodejs-nodemon | before 3.0.3-1.module_el8.10.0+4061+f8ceeab9 | 3.0.3-1.module_el8.10.0+4061+f8ceeab9 |
| AlmaLinux:8 | nodejs-packaging | before 2021.06-5.module_el8.10.0+4084+7c0af990 | 2021.06-5.module_el8.10.0+4084+7c0af990 |
| AlmaLinux:8 | nodejs-packaging | before 2021.06-5.module_el8.10.0+4085+6f807d30 | 2021.06-5.module_el8.10.0+4085+6f807d30 |
| AlmaLinux:8 | nodejs-packaging | before 2021.06-6.module_el8.10.0+4086+70facd4a | 2021.06-6.module_el8.10.0+4086+70facd4a |
| AlmaLinux:8 | nodejs-packaging-bundler | before 2021.06-5.module_el8.10.0+4084+7c0af990 | 2021.06-5.module_el8.10.0+4084+7c0af990 |
| AlmaLinux:8 | nodejs-packaging-bundler | before 2021.06-5.module_el8.10.0+4085+6f807d30 | 2021.06-5.module_el8.10.0+4085+6f807d30 |
| AlmaLinux:8 | nodejs-packaging-bundler | before 2021.06-6.module_el8.10.0+4086+70facd4a | 2021.06-6.module_el8.10.0+4086+70facd4a |
| AlmaLinux:8 | npm | before 1:11.6.2-1.24.13.0.0.module_el8.10.0+4113+bc863bc2 | 1:11.6.2-1.24.13.0.0.module_el8.10.0+4113+bc863bc2 |
| AlmaLinux:8 | npm | before 1:10.9.4-1.22.22.0.1.module_el8.10.0+4112+db1af44b | 1:10.9.4-1.22.22.0.1.module_el8.10.0+4112+db1af44b |
+96
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-27983An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 f58Plan
- CVE-2025-27210An incomplete fix has been identified for CVE-2025-23084 in Node.js, specifically affecting Windows device names like CON, PRN, and AUX.34Monitor
- CVE-2024-27980Due to the improper handling of batch files in child_process.spawn / child_process.spawnSync, a malicious command line argument can inject a32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-23167May 18, 2025 · A flaw in Node.js 20's HTTP parser allows improper termination of HTTP/1 headers using `\r\n\rX` instead of the required `\r\n\r\n`.26Monitor
- ← EarlierCVE-2025-27209Jul 18, 2025 · The V8 release used in Node.js v24.0.0 has changed how string hashes are computed using rapidhash.30Monitor
- Later →CVE-2026-58040Jul 30, 2026 · An incomplete fix has been identified in Node.js: HTTPS Agent TLS session reuse skips hostname verification across identity policies (incomp25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| nodejs node | 10.* | Vendor (CNA) |
| nodejs node | 11.* | Vendor (CNA) |
| nodejs node | 12.* | Vendor (CNA) |
| nodejs node | 13.* | Vendor (CNA) |
| nodejs node | 14.* | Vendor (CNA) |
| nodejs node | 15.* | Vendor (CNA) |
| nodejs node | 16.* | Vendor (CNA) |
| nodejs node | 17.* | Vendor (CNA) |
| nodejs node | 18.* | Vendor (CNA) |
| nodejs node | 4.* | Vendor (CNA) |
| nodejs node | 5.* | Vendor (CNA) |
| nodejs node | 6.* | Vendor (CNA) |
| nodejs node | 7.* | Vendor (CNA) |
| nodejs node | 8.* | Vendor (CNA) |
| nodejs node | 9.* | Vendor (CNA) |
| almalinux:nodejs | 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-devel | 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-docs | 1:22.22.0-3.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs-full-i18n | 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-libs | 1:24.13.0-0.module_el8.10.0+4113+bc863bc2 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-nodemon | 3.0.3-1.module_el8.10.0+4061+f8ceeab9 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging | 2021.06-6.module_el8.10.0+4086+70facd4a · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs-packaging-bundler | 2021.06-6.module_el8.10.0+4086+70facd4a · AlmaLinux:8 | Package registry (OSV) |
| almalinux:nodejs24-docs | 1:24.13.0-1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:nodejs24-npm | 1:11.6.2-1.24.13.0.1.el10_1 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:npm | 1:11.6.2-1.24.13.0.0.module_el8.10.0+4113+bc863bc2 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:v8-13.6-devel | 3:13.6.233.17-1.24.13.0.0.module_el8.10.0+4113+bc863bc2 · AlmaLinux:8 | Package registry (OSV) |
| alpine:nodejs | 22.22.2-r0 · Alpine:v3.21 | Package registry (OSV) |
| debian:nodejs | 18.20.4+dfsg-1~deb12u2 · Debian:12 | Package registry (OSV) |
| opensuse:nodejs20 | 20.20.0-150600.3.15.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
+24
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- Low
Weakness class (CWE)
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
nvd-secondary
Root cause
When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.
The bug in code
The whole CWE-120 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
char buf[256];
memcpy(buf, pkt->data, pkt->len);Fixed
char buf[256];
if (pkt->len > sizeof(buf)) {
return -EINVAL;
}
memcpy(buf, pkt->data, pkt->len);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
- Overflow Variables and TagsCAPEC-46likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- access.redhat.com/errata/RHSA-2026:1842
- access.redhat.com/errata/RHSA-2026:1843
- access.redhat.com/errata/RHSA-2026:2420
- access.redhat.com/errata/RHSA-2026:2421
- access.redhat.com/errata/RHSA-2026:2422
- access.redhat.com/errata/RHSA-2026:2767
- access.redhat.com/errata/RHSA-2026:2768
- access.redhat.com/errata/RHSA-2026:2781
- access.redhat.com/errata/RHSA-2026:2782
- access.redhat.com/errata/RHSA-2026:2783
- access.redhat.com/errata/RHSA-2026:2864
- access.redhat.com/errata/RHSA-2026:2899
- access.redhat.com/errata/RHSA-2026:6402
- access.redhat.com/errata/RHSA-2026:6431
- access.redhat.com/errata/RHSA-2026:7386
- access.redhat.com/errata/RHSA-2026:7387
- access.redhat.com/security/cve/CVE-2025-55131
- bugzilla.redhat.com/show_bug.cgi?id=2431350
- security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-55131.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.