Advisory

GHSA-pmc3-p9hx-jq96

Also known as: CVE-2026-26994, GO-2025-3638

Summary

uTLS ServerHellos are accepted without checking TLS 1.3 downgrade canaries

Details

Description
Before version 1.7.0, 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.

Fix Commit or Pull Request

refraction-networking/utls#337, specifically refraction-networking/utls@f8892761e2a4d29054264651d3a86fda83bc83f9

References

  • https://github.com/refraction-networking/utls/issues/181

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-04-23 14:43 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/refraction-networking/utls

Go · All systems

Affected

  • introduced 0, fixed 1.7.0 (semver)

Fixed versions

1.7.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences