# CVE-2026-118682: ClashMi through 1.0.32.1801 Disabled TLS Certificate Validation Enables Update MITM


- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-wvpm-52pr-rww8

## What is CVE-2026-118682?

CVE-2026-118682 is a high-severity vulnerability in KaringX clashmi, published on 28 Oct 2026. 

### Official description

KaringX ClashMi through 1.0.32.1801 disables TLS certificate validation by default in the HttpUtils helper, allowing attackers to intercept HTTPS traffic by presenting any certificate. Attackers operating the user's proxy node can serve a forged update manifest omitting sha256 to deliver a malicious installer, achieving code execution when the update runs.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2026-118682 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118682 is a high-severity vulnerability in KaringX clashmi, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118682 in the wild and no public exploit code.

Affected product: KaringX clashmi. 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-118682/ (Markdown: https://insights.sbomify.com/CVE-2026-118682/index.md)
```

## Sources

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

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