Summary
The padding extension was incorrectly removed in utls for the non-pq variant of Chrome 120 fingerprint. Chrome removed this extension only when sending pq keyshares. Only this fingerprint is affected since newer fingerprints have pq keyshares by default and older fingerprints have this extension.
Affected symbols: HelloChrome_120
Fix commit: 8fe0b08e9a0e7e2d08b268f451f2c79962e6acd0
Thanks to telegram @acgdaily for reporting this issue.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-26995? CVE-2026-26995 is a low-severity security vulnerability in github.com/refraction-networking/utls (go), affecting versions >= 1.6.0, < 1.8.2. It is fixed in 1.8.2.
- Which versions of github.com/refraction-networking/utls are affected by CVE-2026-26995? github.com/refraction-networking/utls (go) versions >= 1.6.0, < 1.8.2 is affected.
- Is there a fix for CVE-2026-26995? Yes. CVE-2026-26995 is fixed in 1.8.2. Upgrade to this version or later.
- Is CVE-2026-26995 exploitable, and should I be worried? Whether CVE-2026-26995 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-26995 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-26995? Upgrade
github.com/refraction-networking/utlsto 1.8.2 or later.