All vulnerabilities

Servers and applications

CVE-2026-49406

BYONM module resolution allows `package.json` main path traversal to bypass `--allow-read` restrictions

Severity
Medium 5.5
Published
27 May 2026
Last changed
25 Oct 2026
Added to UpHeron
1 Nov 2026
Fixed in
2.7.12
Exploit chance
0.2% in the next 30 daysHigher than 7% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Path traversal (CWE-22)
Attack
Needs local access · Needs a user account · No user action needed
Attacker can
Read data
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Also known as
GHSA-968w-xfqw-vp9q
Sources
NVD, Project advisories (GitHub)

Description

When Deno was run in BYONM mode (nodeModulesDir: "manual"), the module resolver did not validate that a package's resolved entrypoint stayed within its node_modules// directory. A malicious package.json whose main field contained .. segments was able to resolve to an arbitrary path on disk, and the resolver then read that file without consulting the --allow-read allowlist. This let a require("evil-pkg") call return the contents of a file that a direct Deno.readTextFileSync(...) call would have been blocked from reading.

In BYONM mode, Deno resolved npm packages directly from a user-managed node_modules tree. Resolution of require("pkg") proceeded by reading pkg/package.json, taking the main field, joining it to the package directory, and loading the result as a module.

The path joined from main was not constrained to the package root. A package.json such as:

From denoland/deno's security advisory. Shortened; the full text is there.

Workarounds

Users on unpatched versions could mitigate by:

  • Avoiding BYONM mode (nodeModulesDir: "manual") for projects that depended on untrusted packages.
  • Auditing package.json main fields in node_modules for .. segments before running.
  • Granting --allow-read only when the read scope already covered every file the OS user could see (in which case there was no boundary to bypass and no additional exposure).
Workarounds as given by denoland/deno's security advisory.

Affected software

SoftwareAffected versions
DenoServers and applications · cpe:a:deno:deno
  • Every version before 2.7.12
DenoServers and applications · github:denoland/deno
  • Every version before 2.7.12

About Deno

secure runtime for JavaScript and TypeScript based on the V8 JavaScript engine and the Rust programming language

From Wikidata, CC0 1.0.
Monthly active users
400k+Deno
Developers who used it in the past year
4%Stack Overflow Developer Survey 2025, 2025
Weekly downloads (npm)
530,707npm, 15 Nov 2026
Downloads in the last 90 days (crates.io)
2,447crates.io, 15 Nov 2026
Total downloads (crates.io)
634,116crates.io, 15 Nov 2026
Docker Hub pulls
9,367,609Docker Hub, 15 Nov 2026
GitHub stars
108,888GitHub, 15 Nov 2026
Forks
7,444GitHub, 15 Nov 2026
Latest release
v2.9.8GitHub, 15 Nov 2026
Released
21 Oct 2026GitHub
Developer
Ryan DahlWikidata
License
MIT LicenseWikidata
Written in
Rust, TypeScript, JavaScriptWikidata
First released
13 May 2018Wikidata
First published on GitHub
15 May 2018GitHub

Release lines

ReleaseLatestSecurity fixes
2.92.9.8Yes
2.82.8.3Ended 25 Jun 2026
2.72.7.14Ended 22 May 2026
2.62.6.10Ended 25 Feb 2026
2.5 (LTS)LTS2.5.7Ended 30 Apr 2026
2.42.4.5Ended 10 Sept 2025

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-49406
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-49406
  • GitHub Advisory Database https://github.com/advisories/GHSA-968w-xfqw-vp9q
  • github.com https://github.com/denoland/deno/security/advisories/GHSA-968w-xfqw-vp9q