CVE-2026-49401: Unicode Path Permission Bypass in Deno on macOS
- Vendor
- Deno
Deno versions before 2.7.14 contain a permission-check bypass on macOS caused by differences between raw-byte pathname comparisons and APFS path-equivalence behavior. Checks for --deny-read, --deny-write, --deny-run, and --deny-ffi distinguish path spellings that the filesystem resolves to the same object. An attacker-controlled program can use an equivalent Unicode spelling, or a case-equivalent spelling on case-insensitive volumes, to access a denied path despite the configured restriction.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Programs with otherwise sufficient allow permissions can bypass explicit deny-rule carve-outs to read sensitive files, modify protected data, execute denied programs, or load denied native libraries through FFI. Potential consequences include sensitive-data disclosure, data corruption, configuration hijacking, and code execution. Access remains bounded by the operating-system permissions of the Deno process.
Mitigation
If you can’t patch tonight, do this now.
If upgrading immediately is not possible, replace broad allow permissions with narrowly scoped --allow-* allowlists rather than relying on --deny-* exceptions. Allow rules match the original specifier, preventing alternate spellings from matching paths that were not explicitly granted. Do not treat pathname case differences on default case-insensitive APFS volumes as a security boundary.
Remediation
Patch, then assume compromise.
Upgrade Deno to version 2.7.14 or later. The fix normalizes both requested paths and deny-rule paths to NFC and applies Unicode case folding before comparison on macOS.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-49401 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-49401 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-49401?
- Yes. As of Nov 17, 2026, Mallory has reports of a public exploit for CVE-2026-49401.
- Is there a patch for CVE-2026-49401?
- Upgrade Deno to version 2.7.14 or later. The fix normalizes both requested paths and deny-rule paths to NFC and applies Unicode case folding before comparison on macOS.
- What products are affected by CVE-2026-49401?
- Deno.
- How severe is CVE-2026-49401?
- CVE-2026-49401 has a CVSS v3.1 score of 8.4 (High) and an EPSS score of 0.20% (9th percentile) as of Nov 17, 2026.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.