Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
uTLS (github.com/refraction-networking/utls) versions before 1.7.0 do not check the TLS 1.3 downgrade canary in the ServerHello random field when a utls ClientHello spec is used. An active network attacker can alter the ClientHello to remove the SupportedVersions extension, forcing a downgrade to TLS 1.2 that the client accepts without detecting it, and the attack can also be used to fingerprint utls connections. Upgrade to version 1.7.0 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.5 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0030, the 23rd percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:14 UTC First seen by agentprime
- 31 Oct 2026, 14:14 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-pmc3-p9hx-jq96
- OSV: GHSA-pmc3-p9hx-jq96
- github.com/refraction-networking/utls/security/advisories/GHSA-pmc3-p9hx-jq96
- nvd.nist.gov/vuln/detail/CVE-2026-26994
- github.com/refraction-networking/utls/issues/181
- github.com/refraction-networking/utls/pull/337
- github.com/refraction-networking/utls/commit/f8892761e2a4d29054264651d3a86fda83bc83f9
- github.com/refraction-networking/utls