Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.7.12, 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/<pkg>/ 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. This vulnerability is fixed in 2.7.12.
References
| Link | Resource |
|---|---|
| https://github.com/denoland/deno/security/advisories/GHSA-968w-xfqw-vp9q | Exploit Mitigation Vendor Advisory |
| https://github.com/denoland/deno/security/advisories/GHSA-968w-xfqw-vp9q | Exploit Mitigation Vendor Advisory |
Configurations
History
No history.
Information
Published : 2026-06-23 18:18
Updated : 2026-06-26 17:29
NVD link : CVE-2026-49406
Mitre link : CVE-2026-49406
CVE.ORG link : CVE-2026-49406
JSON object : View
Products Affected
deno
- deno
CWE
CWE-22
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
