CVE-2026-26994
uTLS is a fork of crypto/tls, created to customize ClientHello for …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/refraction-networking/utls/security/advisories/GHSA-pmc3-p9hx-jq96
- github.com/refraction-networking/utls/issues/181
- github.com/refraction-networking/utls/pull/337
- github.com/refraction-networking/utls/commit/f8892761e2a4d29054264651d3a86fda83bc83f9
- github.com/advisories/GHSA-pmc3-p9hx-jq96
- nvd.nist.gov/vuln/detail/CVE-2026-26994
- nvd.nist.gov/vuln/detail/CVE-2026-26994
- cve.org/CVERecord?id=CVE-2026-26994
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.