# CVE-2026-26995: uTLS has a fingerprint vulnerability from missing padding extension for Chrome 120


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Updated:** 20 Feb 2026
- **Also known as:** GHSA-rrxv-pmq9-x67r, GO-2026-4512

## What is CVE-2026-26995?

CVE-2026-26995 is a vulnerability in github.com/refraction-networking/utls. 

### Official description

Further research determined the issue is an external dependency vulnerability.

## Which versions are affected by CVE-2026-26995?

3 open source packages ship an affected version, including github.com/refraction-networking/utls.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/refraction-networking/utls` | Go | From 1.6.0 | 1.8.2 |
| `github.com/refraction-networking/utls` | Go | From 1.6.0 | 1.8.2 |
| `github.com/refraction-networking/utls` | Go | From 1.6.0 | 1.8.2 |

## How do I fix CVE-2026-26995?

Upgrade github.com/refraction-networking/utls to 1.8.2 or later.

## Is CVE-2026-26995 being exploited?

There is no known exploitation of CVE-2026-26995 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26995 and fix it if it is affected.

What it is: CVE-2026-26995 is a vulnerability in github.com/refraction-networking/utls. 
Exploitation: There is no known exploitation of CVE-2026-26995 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/refraction-networking/utls (Go): affected from 1.6.0; fixed in 1.8.2
- github.com/refraction-networking/utls (Go): affected from 1.6.0; fixed in 1.8.2
- github.com/refraction-networking/utls (Go): affected from 1.6.0; fixed in 1.8.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26995/ (Markdown: https://insights.sbomify.com/CVE-2026-26995/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26995
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26995
- OSV: https://osv.dev/vulnerability/CVE-2026-26995

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26995/
Summaries are generated and may contain mistakes; the official description above is the record.