Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-49401: Unicode Path Permission Bypass in Deno on macOS

Published Jun 23, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 3 in a dayToday
CVSS8.4High · v3.1
EPSS0.20%9th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Deno
IdentifiersCVE-2026-49401CWE-176 · Improper Handling of Unicode…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
DenoDenoapplication
FAQ

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.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.