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

> Attackers can bypass Node.js permission model restrictions to write trace logs outside allowed directories, potentially exposing sensitive data.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** ALPINE-CVE-2026-56847, AZL-94340, BELL-CVE-2026-56847, BIT-node-2026-56847, BIT-node-min-2026-56847, CLEANSTART-2026-CD76085, DEBIAN-CVE-2026-56847, ECHO-305c-5f8c-08a6, GHSA-hw7r-7v27-7388, MINI-2q3m-xc7p-5x58, MINI-39m3-r32r-32xp, MINI-86p9-vxq9-vv77, MINI-9jp3-2ppm-ggvv, MINI-j7p8-w5fm-j6h9, MINI-pvw8-hc36-8xr8, MINI-rj93-6gpm-c3r3, MINI-x8g3-jpg7-hq9r, UBUNTU-CVE-2026-56847

## What is CVE-2026-56847?

CVE-2026-56847 is a low-severity vulnerability in Nodejs Node.js, published on 30 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 `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`.

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-1119 (Excessive Use of Unconditional Branching)

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

2 open source packages ship an affected version, including node and node-min. It affects 1 product.


| 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 |

Products: Nodejs Node.js.

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

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

## Is CVE-2026-56847 being exploited?

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

Public exploit code:

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

## Other vulnerabilities in Nodejs Node.js

- [CVE-2023-32002](https://insights.sbomify.com/CVE-2023-32002/): Security feature bypass in Node (critical 9.8)
- [CVE-2016-6303](https://insights.sbomify.com/CVE-2016-6303/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-15896](https://insights.sbomify.com/CVE-2017-15896/): Security feature bypass in Node.js (critical 9.1)
- [CVE-2018-7160](https://insights.sbomify.com/CVE-2018-7160/): Server-side request forgery in Node.js (high 8.8)
- [CVE-2018-12120](https://insights.sbomify.com/CVE-2018-12120/): Misconfiguration in Node.js (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56847 is a low-severity vulnerability in Nodejs Node.js, published on 30 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-56847 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-56847/ (Markdown: https://insights.sbomify.com/CVE-2026-56847/index.md)
```

## Sources

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

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