← Back to results
Vulnerability record · public intelligence
CVE-2026-21636
CRITICAL

CVE-2026-21636

Published Jan 20, 2026 · Updated Oct 23, 2026 · Also known as BIT-node-min-2026-21636, BIT-node-2026-21636

Severity · CVSSCRITICAL · 10.0
Known exploitationNot listed
EPSS / likelihood0.87%
QFinch risk score20 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

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

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

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.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSS
SSVC priority
MEDIUM
Confidence
20%
Aliases
BIT-node-min-2026-21636, BIT-node-2026-21636

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. nodejs.org ↗

Record history

Published Jan 20, 2026 · Last refreshed Oct 23, 2026