CVE-2026-49401: Deno Permission Bypass via Unicode Normalization Mismatch on macOS (APFS)

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7.14, Deno’s permission system enforces filesystem and execution restrictions by comparing the requested path against the path supplied to --deny-read, --deny-write, --deny-run, or --deny-ffi. On macOS, that comparison was done at the raw-byte level while the APFS filesystem treats different Unicode spellings of the same name as the same file. That means a program could reach a denied path by spelling it differently than the deny rule. This vulnerability is fixed in 2.7.14.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-06-23).

Weakness: CWE-41: Improper Resolution of Path Equivalence; CWE-176: Improper Handling of Unicode Encoding

How it can be exploited

Exploitable with local access with low attack complexity needing low privileges and no user interaction. Impact: confidentiality low, integrity high, availability none. CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N

CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer has no public exploit code naming this CVE. Check Exploit Observer for anything new.

Live scores

EPSS
0.002
low predicted chance of attack
VEDAS
0.049
little exploit evidence
On CISA KEV
Not listed
Detection rule
Out of scope (local)

Who is affected

ProductAffectedNot affected
Denoland denoversion < 2.7.14Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

This bug needs local access to exploit. VEDAS signatures cover remotely exploitable bugs for now, so there is no network rule or remote check for it. Patch it and watch your endpoint telemetry for unusual local activity.

Advisories on this CVE

References

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.

Supporting partners