Advisory

GHSA-7m29-f4hw-g2vx

Also known as: CVE-2026-27017, GO-2026-4509

Summary

uTLS has a fingerprint vulnerability from GREASE ECH mismatch for Chrome parrots

Details

There is a fingerprint mismatch with Chrome when using GREASE ECH, having to do with ciphersuite selection. When Chrome selects the preferred ciphersuite in the outer ClientHello and the ciphersuite for ECH, it does so consistently based on hardware support. That means, for example, if it prefers AES for the outer ciphersuite, it would also use AES for ECH. The Chrome parrot in utls hardcodes AES preference for outer ciphersuites but selects the ECH ciphersuite randomly between AES and ChaCha20. So there is a 50% chance of selecting ChaCha20 for ECH while using AES for the outer ciphersuite, which is impossible in Chrome.

This is only a problem in GREASE ECH, since in real ECH Chrome selects the first valid ciphersuite when AES is preferred, which is the same in utls. So no change is done there.

Affected symbols: HelloChrome_120, HelloChrome_120_PQ, HelloChrome_131, HelloChrome_133

Fix commit: 24bd1e05a788c1add7f3037f4532ea552b2cee07

Thanks to telegram @acgdaily for reporting this issue.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-02-18 22:33 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/refraction-networking/utls

Go · All systems

Affected

  • introduced 1.6.0, fixed 1.8.1 (semver)

Fixed versions

1.8.1

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