{"answers":{"affected":"2 open source packages ship an affected version, including deno. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44726 in the wild and no public exploit code.","fix":"Upgrade deno to 2.7.8 or later.","what":"CVE-2026-44726 is a high-severity vulnerability in denoland deno, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44726 and fix it if it is affected.\n\nWhat it is: CVE-2026-44726 is a high-severity vulnerability in denoland deno, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-44726 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- deno (crates.io): affected from 2.0.0; fixed in 2.7.8\n- deno (crates.io): affected from 2.0.0; fixed in 2.7.8\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-44726/ (Markdown: https://insights.sbomify.com/CVE-2026-44726/index.md)","id":"CVE-2026-44726","markdown":"https://insights.sbomify.com/CVE-2026-44726/index.md","name":"CVE-2026-44726","record":{"aliases":["GHSA-chqv-56wv-7564","JLSEC-2026-654"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Deno runtime","requires_auth":"none","summary":"A network attacker can force plaintext transmission in Deno's TLS layer by triggering a connection retry, allowing them to observe or tamper with supposedly encrypted traffic.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"deno","vendor":"deno"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"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.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Deno: TLS retry copies stale upgrade hook, risking plaintext traffic","id":"CVE-2026-44726","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Jupyter Server: Stored XSS in `NbconvertFileHandler` / `NbconvertPostHandler` via missing `sandbox` CSP","id":"CVE-2026-44727"},"packages":[{"ecosystem":"crates.io","fixed":["2.7.8"],"introduced":["2.0.0"],"last_affected":[],"package":"deno","purl":null,"source":"GHSA-chqv-56wv-7564"},{"ecosystem":"crates.io","fixed":["2.7.8"],"introduced":["2.0.0"],"last_affected":[],"package":"deno","purl":"pkg:cargo/deno","source":"GHSA-chqv-56wv-7564"}],"prev":{"headline":"EMQX: Stale plugins allow grants amplify a compromised admin/API key to remote code execution","id":"CVE-2026-44725"},"products":["deno"],"published":"2026-06-23","related":[{"cvss_score":10,"headline":"Deno improperly handles resizable ArrayBuffer","id":"CVE-2023-28445","kev_date_added":null,"published":"2023-03-23"},{"cvss_score":10,"headline":"Sandbox bypass leading to arbitrary code execution in Deno","id":"CVE-2022-24783","kev_date_added":null,"published":"2022-03-25"},{"cvss_score":9.8,"headline":"Static imports inside dynamically imported modules do not adhere to permission checks","id":"CVE-2021-32619","kev_date_added":null,"published":"2021-05-28"},{"cvss_score":9.2,"headline":"Deno node:crypto doesn't finalize cipher","id":"CVE-2026-22863","kev_date_added":null,"published":"2026-01-15"},{"cvss_score":8.8,"headline":"Deno interactive permission prompt spoofing via improper ANSI stripping","id":"CVE-2024-27936","kev_date_added":null,"published":"2024-03-06"},{"cvss_score":8.8,"headline":"Deno is vulnerable to interactive `run` permission prompt spoofing via improper ANSI neutralization","id":"CVE-2023-28446","kev_date_added":null,"published":"2023-03-24"},{"cvss_score":8.6,"headline":"Deno missing \"--allow-net\" permission check for built-in Node modules","id":"CVE-2023-33966","kev_date_added":null,"published":"2023-05-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-25","vendors":["denoland"]},"summary":"A network attacker can force plaintext transmission in Deno's TLS layer by triggering a connection retry, allowing them to observe or tamper with supposedly encrypted traffic.","url":"https://insights.sbomify.com/CVE-2026-44726/"}