Advisory

GHSA-83pc-3rw9-qpwj

Also known as: CVE-2026-49860

Summary

Deno: WebSocket API sandbox bypass via missing post-DNS check

Details

Summary

When a WebSocket connection was opened, Deno checked the destination hostname
against --deny-net rules but did not re-check the IP addresses that hostname
resolved to. An attacker-controlled script could use a specially crafted domain
name that passes the hostname check yet resolves to a denied IP, bypassing the
network restriction entirely.

Impact

Code running under --deny-net could connect to hosts that the user intended
to block. In practice this means network isolation rules — for example,
blocking access to localhost or internal services — could be silently
circumvented by a malicious or compromised dependency.

Deno.connect and fetch() were not affected by this specific issue (a
companion advisory covers fetch()).

Who is affected

Users who:

  • run untrusted or third-party code with deno run, and
  • rely on --deny-net to restrict which hosts that code can reach.

If you do not use --deny-net, or if you only run fully trusted code, you are
not affected.

Workaround

No workaround is available short of upgrading. If upgrading immediately is not
possible, avoid granting --allow-net to untrusted code that also has
--deny-net restrictions you depend on for security.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-06-16 19:04 UTC
Modified
2026-07-20 21:15 UTC

Affected packages and fixes

deno

crates.io · All systems

Affected

  • introduced 0, fixed 2.8.1 (semver)

Fixed versions

2.8.1

Fix

  • Fixed version 2.8.1
    cargo update -p deno --precise 2.8.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences