nodejs · Node.js · published 2026-07-30

CVE-2026-58043

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-58043 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 12% of all CVEs. This Node.js vulnerability: CVSS 7.5 (v3.0), a successful attack gives total control of the component. Fixed upstream in Node.js 26.5.1, 24.18.1, 22.23.2. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Node.js 26.5.1, 24.18.1, 22.23.2.

Patch events

  1. This monthSecurity release

    Language runtimeNode.js

    Node.js security releases: 26.5.1, 24.18.1, 22.23.2

    Upgrade to 26.5.124.18.122.23.2

    Why: Vendor security release for server software (most severe: CVE-2026-56846).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (13th pct)FIRST EPSS v2026.06.15
CVSS base score7.5 (v3.0)
CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

A flaw in Node.js Permission Model enforcement can over-grant filesystem access across radix-tree prefix boundaries. Under `--permission`, an attacker who is granted access to one path can abuse boundary handling to read from or write to paths outside the intended filesystem allowlist. This vulnerability affects Node.js **main**, **22.x**, **24.x**, and **26.x**.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →