Deno is a JavaScript, TypeScript, and WebAssembly runtime. Prior to 2.8.0, the Node.js compatibility TCP path checked the permission against the original hostname string before resolution and then did not re-check after resolution. A caller could therefore pass a numeric alias of an IP address (for example the decimal integer 2130706433 or the hex form 0x7f000001, both of which resolve to 127.0.0.1) and reach the denied destination through node:net.connect or node:http.request's { host, port } options form. This vulnerability is fixed in 2.8.0.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/denoland/deno/security/advisories/GHSA-v8fw-85r8-5m23 Exploit, Mitigation, Third Party Advisory
- https://github.com/denoland/deno/security/advisories/GHSA-v8fw-85r8-5m23 Exploit, Mitigation, Third Party 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 6.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-v8fw-85r8-5m23 Exploit, Mitigation, Third Party Advisory
- https://github.com/denoland/deno/security/advisories/GHSA-v8fw-85r8-5m23 Exploit, Mitigation, Third Party Advisory