Quick answers
- Is CVE-2026-49411 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49411 being exploited in the wild.
- How severe is CVE-2026-49411?
- Medium severity, with a CVSS score of 6.5, published 23 June 2026.
- Which products and versions are affected?
- deno (crates.io) <= 2.7.14.
- Is there a fix for CVE-2026-49411?
- A patch was published on 2026-05-27: Fixed in version 2.8.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49411 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-49411?
- 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.
Technical details
A vulnerability exists in Deno's Node.js compatibility TCP path (specifically affecting node:net.connect and node:http.request when using the options object form). The runtime checks network permissions against the raw hostname string provided by the caller but fails to re-check permissions after the hostname is resolved to an IP address. An attacker can exploit this by providing numeric aliases of IP addresses (e.g., decimal 2130706433 or hex 0x7f000001 for 127.0.0.1), which bypasses string-based 'deny' rules. This allows unauthorized access to restricted network destinations like loopback or internal IP ranges. The issue is fixed in version 2.8.0; native Deno APIs and URL-string based requests are not affected as they perform proper normalization or post-resolution checks.
Affected products
- denoland deno < 2.8.0
Identifiers
- CVE-2026-49411
- GHSA-v8fw-85r8-5m23
Timeline
- 2026-05-27: advisory: GitHub advisory published by maintainers
- 2026-06-23: disclosed: CVE published to NVD
- 2026-05-27: patched: Fixed in version 2.8.0