Client fingerprint disclosure via inconsistent GREASE ECH ciphers
Published Feb 20, 2026 · Updated Feb 20, 2026
Fingerprint disclosure in Refraction Networking uTLS 1.6.0 through 1.8.0 allows remote attackers to identify Chrome-parrot clients via GREASE ECH. BoringGREASEECH offers both AES-GCM and ChaCha20 while the outer Chrome-parrot ClientHello always prefers AES, producing an impossible Chrome combination half the time. Exposure requires an affected Chrome ClientHello symbol and GREASE ECH; real ECH is unaffected, and the consequence is limited to loss of fingerprint resistance.
Summary
What happened
Fingerprint disclosure in Refraction Networking uTLS 1.6.0 through 1.8.0 allows remote attackers to identify Chrome-parrot clients via GREASE ECH. BoringGREASEECH offers both AES-GCM and ChaCha20 while the outer Chrome-parrot ClientHello always prefers AES, producing an impossible Chrome combination half the time. Exposure requires an affected Chrome ClientHello symbol and GREASE ECH; real ECH is unaffected, and the consequence is limited to loss of fingerprint resistance.
The record
- CVE
- CVE-2026-27017
- Published
- Feb 20, 2026
- Updated
- Feb 20, 2026
- Vendor
- Refraction Networking
- Product
- uTLS
- Classifications
- CWE-1240
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2026CVE publishedPublication date reported by the CVE source.
- Feb 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.6.0, < 1.8.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo