# CVE-2026-56847 — nodejs node

> As of 2026-07-30, CVE-2026-56847 is a LOW-severity vulnerability in nodejs node, CVSS v3.1 3.3, EPSS 0.1% (4.9th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-56847, most recently “Node.js Patches 11 Security Flaws Across v22.23.2, v24.18.1, v26.5.1 (HTTP/2 DoS, Permission Model Bypass, TLS/mTLS Issues)”.

**Last updated:** 2026-07-30

## What is CVE-2026-56847?

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

The record classifies CVE-2026-56847 under weakness class [CWE-1119](https://cwe.mitre.org/data/definitions/1119.html). Its CVSS v3 base vector states that the flaw requires local access to the host, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 67 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 3.3 — LOW (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **EPSS (FIRST):** 0.1% probability of exploitation in the next 30 days, higher than 4.9% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 1.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-30

## Is CVE-2026-56847 being exploited?

No public exploitation evidence for CVE-2026-56847 is recorded in the sources Threadlinqs tracks — CISA KEV, Exploit-DB, public proof-of-concept repositories and ProjectDiscovery Nuclei — as of 2026-07-30. That is an absence of evidence in those feeds, not a guarantee that the vulnerability is unexploited.

## Affected products and versions

- [nodejs](https://intel.threadlinqs.com/vendors/nodejs): node

## How to fix CVE-2026-56847

No vendor patch reference has been recorded for CVE-2026-56847 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-56847

1 tracked threat in the Threadlinqs corpus references CVE-2026-56847, either in the campaign’s CVE list or as an indicator on the campaign record.

- [Node.js Patches 11 Security Flaws Across v22.23.2, v24.18.1, v26.5.1 (HTTP/2 DoS, Permission Model Bypass, TLS/mTLS Issues)](https://intel.threadlinqs.com/threat/TL-2026-1807) — HIGH · 2026-08-01

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on 2026-08-01. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

- [nodejs.org](https://nodejs.org/en/blog/vulnerability/july-2026-security-releases)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-56847
Full detection coverage and IOCs for threats exploiting CVE-2026-56847 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp