# CVE-2026-106781: An issue in WCH CH340/CH341 USB-to-Serial Windows Driver setup package CH341SER.EXE version 4.0 allows a local attacker to escalate privileges.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-vcm3-cv68-2c35

## What is CVE-2026-106781?

CVE-2026-106781 is a vulnerability in n/a, published on 26 Oct 2026. 

### Official description

An issue in WCH CH340/CH341 USB-to-Serial Windows Driver setup package CH341SER.EXE version 4.0 allows a local attacker to escalate privileges.

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


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

No fix has been published for CVE-2026-106781 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-106781 being exploited?

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

Public exploit code:

- CVE-2026-106781 CH341SER Driver Installer Privilege Escalation (github_poc): https://github.com/tanuj8124/CVE-2026-106781

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106781 is a vulnerability in n/a, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-106781 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-106781/ (Markdown: https://insights.sbomify.com/CVE-2026-106781/index.md)
```

## Sources

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

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