CVE-2026-56847: Low severity OpenJS Node.js vulnerability

Published Jul 30, 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.

Affected Software

2 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

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

Event History

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
DescriptionSeverityWeakness
Aug 7, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:01 AM
Affected Software
Updated
via Microsoft·08:01 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

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