CVE-2026-56847: Permission Model Bypass: `trace_events.createTracing().enable()` Writes Trace Logs Outside `--allow-fs-write`

Published Jul 29, 2026
·
Updated

A flaw in Node.js Permission Model enforcement allows traceevents.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.

Other sources

A flaw in Node.js Permission Model enforcement allows traceevents.createTracing().enable() to write trace logs outside --allow-fs-write paths.

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

— Node.Js

Affected Software

14 affected componentsFixes available
OpenJS Node.js>22.0.0<23.0.0, >24.0.0<25.0.0, >26.0.0<27.0.0
Microsoft azl3 nodejs 24.17.0-1<24.18.1-1
24.18.1-1
Node.js Node.js>=22.0.0<22.23.2, >=24.0.0<24.18.1, >=26.0.0<26.5.1
22.23.224.18.126.5.1
Node.js Node.js>=22.0.0<22.23.2
22.23.2
Node.js Node.js>=24.0.0<24.18.1
24.18.1
Node.js Node.js>=26.0.0<26.5.1
26.5.1
Nodejs Node.js>=22.0<=22.23.1
Nodejs Node.js>=24.0.0<=24.18.0
Nodejs Node.js>=26.0.0<=26.5.0
alpine/nodejs<22.23.2-r0
22.23.2-r0
alpine/nodejs<22.23.2-r0
22.23.2-r0
alpine/nodejs<24.18.1-r0
24.18.1-r0
alpine/nodejs<24.18.1-r0
24.18.1-r0
alpine/nodejs-current<26.5.1-r0
26.5.1-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 24.18.1-1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 22.23.2Fixed in 24.18.1Fixed in 26.5.1
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 22.23.2
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 24.18.1
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 26.5.1
  6. Upgrade

    Upgrade alpine/nodejs to a version that resolves this vulnerability.

    Fixed in 22.23.2-r0
  7. Upgrade

    Upgrade alpine/nodejs to a version that resolves this vulnerability.

    Fixed in 24.18.1-r0
  8. Upgrade

    Upgrade alpine/nodejs-current to a version that resolves this vulnerability.

    Fixed in 26.5.1-r0

Event History

Jul 29, 2026
CVE Published
via Node.js·12:00 AM
Data Sourced
via Node.js·12:00 AM
DescriptionSeverityAffected Software
Jul 30, 2026
CVE Published
via MITRE·06:02 AM
Data Sourced
via MITRE·06:02 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:25 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·06:25 AM
Affected Software
Aug 7, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeaknessAffected Software
Oct 23, 2026
Exploit Published
via GitHub·11:45 PM

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-56847?

The severity of CVE-2026-56847 is categorized as low with a score of 3.3.

2

How do I fix CVE-2026-56847?

To mitigate CVE-2026-56847, ensure that Node.js is updated to the latest version which addresses this vulnerability.

3

What impact does CVE-2026-56847 have?

CVE-2026-56847 may lead to a confidentiality impact or bypass of the intended security boundary under affected configurations.

4

Which versions of Node.js are affected by CVE-2026-56847?

CVE-2026-56847 affects Node.js version 22.x.

5

What steps can I take to secure my application against CVE-2026-56847?

Securing your application against CVE-2026-56847 involves applying security patches and reviewing your application’s permission model for exposure.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203