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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- 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
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.5 · denoNVD modified 2026-10-25 23:10
Affected (CPE criteria) 1
cpe:2.3:a:deno:deno:*:*:*:*:*:*:*:*
References 2
- 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