Skip to content
Noroxi
NVD / CVE Program· CNA hackerone

CVE-2026-56847: A flaw in Node.js Permission Model enforcement allows `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`.

Noroxi assessment

Priority: Monitor (action score 24/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: azl3 nodejs 24.17.0-1 on Azure Linux 3.0 24.18.1-1.
  • Severity is disputed: the assigning authority (CNA) scores it 3.3, NVD 6.1.

Low priority for now. Upgrade to azl3 nodejs 24.17.0-1 on Azure Linux 3.0 24.18.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

MediumCVSS 6.1 · v3.1—Proof of concept Fix available
Published
Jul 30, 2026
Updated
Oct 23, 2026
EPSS
0.1% · 4th percentile

Report tools

JSON

Action score

24

Monitor

Low priority for now.

CVSS
24 / 40 · 6.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.1
CNA · hackerone
3.3
2.8 point gap

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-56847

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for nodejs records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
nodejsnode.js

Using node.js? Add it to your stack and be the first to know about CVEs like this one. (Node.js)

Watch new CVEs for node.js

When you'll hear from us

  • when a new CVE affecting this product is published
  • when a record in your stack enters KEV or gets exploit code

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every Monday

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nodejs node.js22.0 and later · up to 22.23.1 inclusive
  • nodejs node.js24.0.0 and later · up to 24.18.0 inclusive
  • nodejs node.js26.0.0 and later · up to 26.5.0 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

  • nodejs node

    • 26.5.0 and later · up to and including 26.5.0affected · semver
    • 24.18.0 and later · up to and including 24.18.0affected · semver
    • 22.23.1 and later · up to and including 22.23.1affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10nodejsbefore 1:22.23.2-1.el10_21:22.23.2-1.el10_2
AlmaLinux:10nodejs-develbefore 1:22.23.2-1.el10_21:22.23.2-1.el10_2
AlmaLinux:10nodejs-docsbefore 1:22.23.2-1.el10_21:22.23.2-1.el10_2
AlmaLinux:10nodejs-full-i18nbefore 1:22.23.2-1.el10_21:22.23.2-1.el10_2
AlmaLinux:10nodejs-libsbefore 1:22.23.2-1.el10_21:22.23.2-1.el10_2
AlmaLinux:10nodejs-npmbefore 1:10.9.8-1.22.23.2.1.el10_21:10.9.8-1.22.23.2.1.el10_2
AlmaLinux:10nodejs24before 1:24.19.0-1.el10_21:24.19.0-1.el10_2
AlmaLinux:10nodejs24-develbefore 1:24.19.0-1.el10_21:24.19.0-1.el10_2
AlmaLinux:10nodejs24-docsbefore 1:24.19.0-1.el10_21:24.19.0-1.el10_2
AlmaLinux:10nodejs24-full-i18nbefore 1:24.19.0-1.el10_21:24.19.0-1.el10_2
AlmaLinux:10nodejs24-libsbefore 1:24.19.0-1.el10_21:24.19.0-1.el10_2
AlmaLinux:10nodejs24-npmbefore 1:11.17.0-1.24.19.0.1.el10_21:11.17.0-1.24.19.0.1.el10_2
AlmaLinux:8nodejsbefore 1:22.23.2-1.module_el8.10.0+4265+75d280861:22.23.2-1.module_el8.10.0+4265+75d28086
AlmaLinux:8nodejsbefore 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a1:24.19.0-1.module_el8.10.0+4268+8e07aa5a
AlmaLinux:8nodejs-develbefore 1:22.23.2-1.module_el8.10.0+4265+75d280861:22.23.2-1.module_el8.10.0+4265+75d28086
AlmaLinux:8nodejs-develbefore 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a1:24.19.0-1.module_el8.10.0+4268+8e07aa5a
AlmaLinux:8nodejs-docsbefore 1:22.23.2-1.module_el8.10.0+4265+75d280861:22.23.2-1.module_el8.10.0+4265+75d28086
AlmaLinux:8nodejs-docsbefore 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a1:24.19.0-1.module_el8.10.0+4268+8e07aa5a
AlmaLinux:8nodejs-full-i18nbefore 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a1:24.19.0-1.module_el8.10.0+4268+8e07aa5a
AlmaLinux:8nodejs-full-i18nbefore 1:22.23.2-1.module_el8.10.0+4265+75d280861:22.23.2-1.module_el8.10.0+4265+75d28086
AlmaLinux:8nodejs-libsbefore 1:22.23.2-1.module_el8.10.0+4265+75d280861:22.23.2-1.module_el8.10.0+4265+75d28086
AlmaLinux:8nodejs-libsbefore 1:24.19.0-1.module_el8.10.0+4268+8e07aa5a1:24.19.0-1.module_el8.10.0+4268+8e07aa5a
AlmaLinux:8nodejs-nodemonbefore 3.1.14-2.module_el8.10.0+4250+09238ed43.1.14-2.module_el8.10.0+4250+09238ed4
AlmaLinux:8nodejs-nodemonbefore 3.1.14-2.module_el8.10.0+4252+aedd4c303.1.14-2.module_el8.10.0+4252+aedd4c30

+96

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

  • CVE-2019-15605HTTP request smuggling in Node.js 10, 12, and 13 causes malicious payload delivery when transfer-encoding is malformed
    56Plan
  • CVE-2021-22883Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an
    53Plan
  • CVE-2021-22930Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory c
    50Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-48935Jun 26, 2026 · A flaw in Node.js Permission API can cause a file metadata to be modified even on a path that was set as read-only with e.g.
    13Monitor
  • ← EarlierCVE-2026-48936Jun 26, 2026 · A flaw in Node.js Permission API can cause a local server to be started (via a Unix domain socket), even without the `--allow-net` permissio
    13Monitor
  • Later →CVE-2026-56850Jul 30, 2026 · A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be
    17Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
azl3 nodejs 24.17.0-1 on Azure Linux 3.024.18.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:nodejs1:22.23.2-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs-devel1:22.23.2-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs-docs1:22.23.2-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs-full-i18n1:22.23.2-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs-libs1:22.23.2-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs-npm1:10.9.8-1.22.23.2.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs241:24.19.0-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs24-devel1:24.19.0-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs24-docs1:24.19.0-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs24-full-i18n1:24.19.0-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs24-libs1:24.19.0-1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:nodejs24-npm1:11.17.0-1.24.19.0.1.el10_2 · AlmaLinux:10Package registry (OSV)
alpine:nodejs22.23.2-r0 · Alpine:v3.21Package registry (OSV)
alpine:nodejs-current26.5.1-r0 · Alpine:v3.24Package registry (OSV)
debian:nodejs20.19.2+dfsg-1+deb13u3 · Debian:13Package registry (OSV)
opensuse:nodejs2222.23.2-160000.1.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:nodejs2424.18.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:nodejs2626.5.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:nodejs220:22.23.2-2.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs22-bin0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs22-devel0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs22-docs0:22.23.2-2.3.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs240:24.18.1-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-bin0:24.18.1-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs260:26.5.1-1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-bin0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-devel0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-docs0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-full-i18n0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)

+5

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-10-23

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+85 d
  3. TodayNov 9, 2026+102 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-1119 · Excessive Use of Unconditional Branching

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturitynone → poc
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records