Skip to main content
VulnerabilityPublished Updated

CVE-2026-49401: denoland deno · Improper Resolution of Path Equivalence

Affects denoland denoSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.3 High : upgrade to 2.7.14 soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.7.14
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade deno and denoland/deno to 2.7.14.

Affected software

ProductAffectedFixed in
denolanddenoAffected
  • <2.7.14
Fixed in
  • 2.7.14
GitHubdenoland/denopkg:github/denoland/denoOther threatsAffected
  • <2.7.14
Fixed in
  • 2.7.14

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Deno to version 2.7.14 or later, where this vulnerability is fixed. No other mitigation is indicated or required.

Description

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.

References

Community reviews

Loading reviews…