denoland · Deno · published 2026-06-23

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

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-49401 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 9% of all CVEs. This Deno vulnerability: CVSS 7.3 (v3.1). Fixed upstream in Deno 2.8.1, 2.8.0, 2.7.14, 2.7.12 (+2 more). Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Deno 2.8.1, 2.8.0, 2.7.14, 2.7.12, 2.7.10, 2.7.8.

Patch events

  1. This monthSecurity release

    Language runtimeDeno

    Deno security fixes: 9 CVEs

    Upgrade to 2.8.12.8.02.7.142.7.122.7.102.7.8

    Why: CVE-2026-49402: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (10th pct)FIRST EPSS v2026.06.15
CVSS base score7.3 (v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →