Skip to content

CVE-2026-44726 Deno: TLS retry copies stale upgrade hook, risking plaintext traffic

CriticalCVSS 9.1 EPSS 0.23%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: total

Description

Deno is a JavaScript, TypeScript, and WebAssembly runtime. From 2.0.0 until 2.7.8, a flaw in Deno's Node.js tls compatibility layer could cause a TLS client to transmit application data in plaintext after a connection retry. When `autoSelectFamily was enabled and the first address-family attempt failed, the socket reinitialization path reused a stale TLS upgrade hook that was bound to the original, failed handle. As a result, the replacement TCP connection was never upgraded to TLS, and any data the application wrote before the secureConnect event travelled over the network unencrypted. A network attacker positioned to cause the initial connection attempt to fail (for example, by dropping IPv6 traffic on a dual-stack host) could deterministically trigger the fallback path and observe or tamper with traffic that the application believed was TLS-protected. This vulnerability is fixed in 2.7.8.

Upgrade path

3 packages: 2 fixed.

PackageAffectedFixed inStatus
crates.io deno(crates.io) >= 2.0.0, < 2.7.8 2.7.8 Fixed
deno >= 2.0.0, < 2.7.8 2.7.8 Fixed
denoland deno = >= 2.0.0, < 2.7.8 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
crates.io deno(crates.io) >= 2.0.0, < 2.7.8 2.7.8
denoland deno = >= 2.0.0, < 2.7.8 No fix listed
deno >= 2.0.0, < 2.7.8 2.7.8

References