CVE-2026-44726 json
Deno: TLS retry copies stale upgrade hook, risking plaintext traffic
published 2026-05-27 5 mo ago modified 2026-10-25 14 d ago also EUVD-2026-38548 , GHSA-chqv-56wv-7564 , JLSEC-2026-654
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- crates.io deno 2.7.8
- julia Deno_jll 2.8.1+0
- deno deno 2.7.8
- deno deno_runtime 2.7.8
- deno serde_v8 2.7.8
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 4 mo ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/denoland/deno/security/advisories/GHSA-chqv-56wv-7564 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | deno | >=2.0.0, <2.7.8 |
2.7.8 |
| julia | Deno_jll | >=2.0.0+0, <2.8.1+0 |
2.8.1+0 |
Affected products
- denoland deno
Classification
- Weakness
-
- CWE-319 Cleartext Transmission of Sensitive Information
References
-
github.com
/denoland/deno/security/advisories/GHSA-chqv-56wv-7564
web, exploit, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-44726
advisory
-
github.com
/denoland/deno
package
-
github.com
/advisories/GHSA-chqv-56wv-7564
web
Sources
- CVE List CVE-2026-44726
- GitHub Advisory GHSA-chqv-56wv-7564
- NVD CVE-2026-44726
- OSV JLSEC-2026-654
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.