denoland · Deno · published 2026-06-23
CVE-2026-44726Deno: TLS retry copies stale upgrade hook, risking plaintext traffic
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-44726 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 14% of all CVEs. This Deno vulnerability: CVSS 7.4 (v3.1), a successful attack gives total control of the component. Fixed upstream in Deno 2.8.1, 2.8.0, 2.7.14, 2.7.12 (+2 more). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Deno 2.8.1, 2.8.0, 2.7.14, 2.7.12, 2.7.10, 2.7.8.
Patch events
Language runtimeDeno
Deno security fixes: 9 CVEs
Upgrade to
2.8.12.8.02.7.142.7.122.7.102.7.8Why: CVE-2026-49402: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (15th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 7.4 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- denoland deno
>= 2.0.0, < 2.7.8(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.