Quick answers
- Is CVE-2026-49406 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49406 being exploited in the wild.
- How severe is CVE-2026-49406?
- Medium severity, with a CVSS score of 5.5, published 23 June 2026.
- Which products and versions are affected?
- deno (crates.io) <= 2.7.11, SEMVER:introduced=0,fixed=2.7.12.
- Is there a fix for CVE-2026-49406?
- Yes. deno (crates.io): upgrade to 2.7.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49406 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-49406?
- Check whether you run deno (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- deno (crates.io): upgrade to 2.7.12 or later
cargo update -p deno
Technical details
A path traversal vulnerability exists in Deno's 'Bring Your Own Node Modules' (BYONM) mode, specifically when 'nodeModulesDir' is set to 'manual'. The module resolver fails to validate that a package's entrypoint, defined in the 'main' field of package.json, remains within the package's directory. By using dot-dot (..) sequences, a malicious package can point its entrypoint to sensitive files elsewhere on the disk (e.g., .env files or credentials). Because the BYONM resolver bypasses the standard '--allow-read' permission checks for paths containing 'node_modules', it can read and return the contents of these files to the application. This vulnerability is fixed in version 2.7.12.
Affected products
- denoland Deno < 2.7.12
Identifiers
- CVE-2026-49406
- GHSA-968w-xfqw-vp9q
Timeline
- 2026-05-27: advisory: GitHub advisory published by maintainers
- 2026-06-23: disclosed: NVD publication date
- 2026-06-23: patched: Fix confirmed in version 2.7.12