CVE-2026-21636: Node.js permission model bypass via unchecked Unix Domain Socket connections (UDS)

Published Jan 13, 2026
·
Updated

A flaw in Node.js's permission model allows Unix Domain Socket (UDS) connections to bypass network restrictions when --permission is enabled. Even without --allow-net, attacker-controlled inputs (such as URLs or socketPath options) can connect to arbitrary local sockets via net, tls, or undici/fetch. This breaks the intended security boundary of the permission model and enables access to privileged local services, potentially leading to privilege escalation, data exposure, or local code execution.

In the moment of this vulnerability, network permissions (--allow-net) are still in the experimental phase.

Other sources

A flaw in Node.js's permission model allows Unix Domain Socket (UDS) connections to bypass network restrictions when --permission is enabled. Even without --allow-net, attacker-controlled inputs (such as URLs or socketPath options) can connect to arbitrary local sockets via net, tls, or undici/fetch. This breaks the intended security boundary of the permission model and enables access to privileged local services, potentially leading to privilege escalation, data exposure, or local code execution.

The issue affects users of the Node.js permission model on version v25.

In the moment of this vulnerability, network permissions (--allow-net) are still in the experimental phase.

— MITRE

Affected Software

5 affected componentsFixes available
npm/node
Nodejs Node.js>=25.0.0<25.3.0
Node.js Node.js>=25.0.0<25.3.0
25.3.0
ubuntu/nodejs*
ubuntu/nodejs*

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 25.3.0

Event History

Jan 13, 2026
CVE Published
via Node.js·12:00 AM
Data Sourced
via Node.js·12:00 AM
DescriptionSeverityAffected Software
Jan 20, 2026
CVE Published
via MITRE·08:41 PM
Data Sourced
via MITRE·08:41 PM
DescriptionSeverity
Data Sourced
via OSV·09:16 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software
Apr 27, 2026
Exploit Published
via GitHub·07:48 PM

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-21636?

CVE-2026-21636 is considered a high severity vulnerability due to its potential to enable unauthorized access to local sockets.

2

How do I fix CVE-2026-21636?

To mitigate CVE-2026-21636, avoid using the `--permission` flag and validate all inputs to ensure they do not include unauthorized socket paths.

3

Who is affected by CVE-2026-21636?

CVE-2026-21636 affects applications using Node.js versions where the permission model allows Unix Domain Socket connections to bypass network restrictions.

4

What impact does CVE-2026-21636 have on system security?

The impact of CVE-2026-21636 could lead to unauthorized data access or manipulation by allowing an attacker to connect to sensitive local sockets.

5

Is CVE-2026-21636 present in all Node.js versions?

CVE-2026-21636 is not present in all Node.js versions; it specifically affects versions where the flawed permission model is implemented.

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