CVE Intelligence
High Memory corruption

CVE-2025-55131 — Classic Buffer Overflow in Nodejs Node

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 Jan 20, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: hackerone

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 3.5% (30-day exploitation probability)+13
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
3.51%
ahead of 89% of scored CVEs · Oct 14, 2026
Affects
Nodejs
Node
CVSS base
7.1
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Nodejs Node).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Nodejs Node ≥ 9.0 and < 9.*≥ 18.0 and < 18.*≥ 17.0 and < 17.*≥ 16.0 and < 16.*≥ 15.0 and < 15.*≥ 14.0 and < 14.*≥ 13.0 and < 13.*≥ 12.0 and < 12.*
and 11 more ≥ 11.0 and < 11.*≥ 10.0 and < 10.*≥ 20.19.6 and ≤ 20.19.6≥ 8.0 and < 8.*≥ 7.0 and < 7.*≥ 6.0 and < 6.*≥ 5.0 and < 5.*≥ 4.0 and < 4.*≥ 25.2.1 and ≤ 25.2.1≥ 24.12.0 and ≤ 24.12.0≥ 22.21.1 and ≤ 22.21.1
Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.1 CVSS 3.1 High 1.6 5.5 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database
7.1 CVSS 3.0 High 1.6 5.5 support@hackerone.com via NIST National Vulnerability Database
7.1 CVSS 3.0 High — — hackerone via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L (score shown at the top: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-120 · Classic Buffer Overflow

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 3.51%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
web/proxy/WAF logsnetwork IDS/IPSendpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · nodejs/node
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 7.1
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Jan 20, 2026 · hackerone

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

20 on the record

Elsewhere on this site

Nodejs
every CVE for this vendor
Memory corruption
same class
CWE-120
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-48936 Improper Access Control in Nodejs Node.js Jun 25, 2026
  • CVE-2026-48935 Incorrect Default Permissions in Nodejs Node.js Jun 25, 2026
  • CVE-2026-48930 Node.js TLS hostname handling flaw enabling silent authority rebinding Jun 25, 2026
  • CVE-2026-48615 A flaw in Node.js proxy tunnel error handling could expose proxy credentials in… Jun 25, 2026
  • CVE-2026-48619 Uncontrolled Resource Consumption in Nodejs Node.js Jun 25, 2026
  • CVE-2026-48933 Integer Overflow or Wraparound in Nodejs Node.js Jun 25, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-55131 is "Classic Buffer Overflow in Nodejs Node", rated High. It affects Node (Nodejs); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.1 describes technical severity. EPSS 3.51% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.