{"answers":{"affected":"3 open source packages ship an affected version, including github.com/refraction-networking/utls. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-26994 in the wild and no public exploit code.","fix":"Upgrade github.com/refraction-networking/utls to 1.7.0 or later.","what":"CVE-2026-26994 is a medium-severity vulnerability in refraction-networking utls, published on 20 Feb 2026."},"fix_prompt":"Check this codebase for CVE-2026-26994 and fix it if it is affected.\n\nWhat it is: CVE-2026-26994 is a medium-severity vulnerability in refraction-networking utls, published on 20 Feb 2026. \nExploitation: There is no known exploitation of CVE-2026-26994 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/refraction-networking/utls (Go): affected all versions; fixed in 1.7.0\n- github.com/refraction-networking/utls (Go): affected all versions; fixed in 1.7.0\n- github.com/refraction-networking/utls (Go): affected from 1.0.0; fixed in 1.7.0\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-26994/ (Markdown: https://insights.sbomify.com/CVE-2026-26994/index.md)","id":"CVE-2026-26994","markdown":"https://insights.sbomify.com/CVE-2026-26994/index.md","name":"CVE-2026-26994","record":{"aliases":["DEBIAN-CVE-2026-26994","GHSA-pmc3-p9hx-jq96","GO-2025-3638","UBUNTU-CVE-2026-26994"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"product":"utls","vendor":"refraction-networking"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"uTLS is a fork of crypto/tls, created to customize ClientHello for fingerprinting resistance while still using it for the handshake. In versions 1.6.7 and below, uTLS did not implement the TLS 1.3 downgrade protection mechanism specified in RFC 8446 Section 4.1.3 when using a uTLS ClientHello spec. This allowed an active network adversary to downgrade TLS 1.3 connections initiated by a uTLS client to a lower TLS version (e.g., TLS 1.2) by modifying the ClientHello message to exclude the SupportedVersions extension, causing the server to respond with a TLS 1.2 ServerHello (along with a downgrade canary in the ServerHello random field). Because uTLS did not check the downgrade canary in the ServerHello random field, clients would accept the downgraded connection without detecting the attack. This attack could also be used by an active network attacker to fingerprint uTLS connections. This issue has been fixed in version 1.7.0.","ecosystems":["Go"],"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":"uTLS ServerHellos are accepted without checking TLS 1.3 downgrade canaries","id":"CVE-2026-26994","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":null,"year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"uTLS has a fingerprint vulnerability from missing padding extension for Chrome 120","id":"CVE-2026-26995"},"packages":[{"ecosystem":"Go","fixed":["1.7.0"],"introduced":["0"],"last_affected":[],"package":"github.com/refraction-networking/utls","purl":null,"source":"GHSA-pmc3-p9hx-jq96"},{"ecosystem":"Go","fixed":["1.7.0"],"introduced":["0"],"last_affected":[],"package":"github.com/refraction-networking/utls","purl":"pkg:golang/github.com/refraction-networking/utls","source":"GHSA-pmc3-p9hx-jq96"},{"ecosystem":"Go","fixed":["1.7.0"],"introduced":["1.0.0"],"last_affected":[],"package":"github.com/refraction-networking/utls","purl":"pkg:golang/github.com/refraction-networking/utls","source":"GO-2025-3638"}],"prev":{"headline":"Flare has XSS vulnerability in Raw File Preview","id":"CVE-2026-26993"},"products":["utls"],"published":"2026-02-20","related":[{"cvss_score":2.3,"headline":"uTLS has a Chrome Parrot Fingerprint Vulnerability due to GREASE ECH Cipher Suite Mismatch","id":"CVE-2026-27017","kev_date_added":null,"published":"2026-02-20"}],"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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-20","vendors":["refraction-networking"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-26994/"}