# CVE-2026-58039: Security feature bypass in node

> Node.js Permission Model flaw allows process.report to write files outside allowed paths, bypassing security boundaries in specific configurations.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** ALPINE-CVE-2026-58039, AZL-94343, BELL-CVE-2026-58039, BIT-node-2026-58039, BIT-node-min-2026-58039, CLEANSTART-2026-SR40385, DEBIAN-CVE-2026-58039, ECHO-069b-5add-3223, GHSA-4qw5-6jhx-9hfx, MINI-7p39-6m5m-87mv, MINI-chx4-7mf7-pmgm, MINI-f4vg-fxqm-qwgr, MINI-jxpx-v692-36mq, MINI-p76j-7cp5-pmvf, MINI-qj28-843c-5v62, MINI-vmxf-6x2v-9j4h, MINI-xh8w-mgxm-4mjg, UBUNTU-CVE-2026-58039

## What is CVE-2026-58039?

CVE-2026-58039 is a low-severity vulnerability in nodejs node, published on 31 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw in Node.js Permission Model enforcement allows process.report writes (and overwrites) files outside --allow-fs-write paths.

This can lead to confidentiality impact or bypass of the intended security boundary under affected configurations.

This vulnerability affects Node.js **22.x**, **24.x**, and **26.x**.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-58039?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | All versions | 22.23.2, 24.18.1, 26.5.1 |
| `node-min` | Bitnami | All versions | 22.23.2, 24.18.1, 26.5.1 |

## How do I fix CVE-2026-58039?

Upgrade node to a fixed version for your release line: 22.23.2, 24.18.1 or 26.5.1.

## Is CVE-2026-58039 being exploited?

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

Public exploit code:

- Offline Node.js evidence checker for CVE-2026-58039: Permission Model process-report filesystem bypass. Single-file Python; JSON/CSV/HTML reports; no exploit payloads. (github_poc): https://github.com/CompleteTech-Security/node-cve-2026-58039-check

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58039 and fix it if it is affected.

What it is: CVE-2026-58039 is a low-severity vulnerability in nodejs node, published on 31 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-58039 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected all versions; fixed in 22.23.2, 24.18.1, 26.5.1
- node-min (Bitnami): affected all versions; fixed in 22.23.2, 24.18.1, 26.5.1

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-2026-58039/ (Markdown: https://insights.sbomify.com/CVE-2026-58039/index.md)
```

## Sources

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

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