# CVE-2026-129118: C-Kermit 8.0.200 before 11.1.515 Improper Certificate Hostname Matching via dNSName_cmp


- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-129118, GHSA-q6vx-pc22-rghc, UBUNTU-CVE-2026-129118

## What is CVE-2026-129118?

CVE-2026-129118 is a high-severity vulnerability in OpenKermit C-Kermit, published on 13 Nov 2026. 

### Official description

C-Kermit 8.0.200 before 11.1.515 contains an improper certificate hostname validation vulnerability that allows attackers to impersonate hosts by abusing wildcard matching in dNSName_cmp() in ck_ssl.c. Attackers holding a trusted certificate with over-matching names containing asterisks, question marks, brackets, or empty labels can intercept credentials and data over Telnet, FTP, and HTTP TLS connections.

Weakness: CWE-297 (Improper Validation of Certificate with Host Mismatch)

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

1 open source package ship an affected version, including openkermit/ckermit.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `openkermit/ckermit` | GitHub | `pkg:github/openkermit/ckermit` | From 8.0.200 | 11.1.515 |

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

Upgrade openkermit/ckermit to 11.1.515 or later.

## Is CVE-2026-129118 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129118 is a high-severity vulnerability in OpenKermit C-Kermit, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129118 in the wild and no public exploit code.

Affected packages and fixed versions:
- openkermit/ckermit (GitHub): affected from 8.0.200; fixed in 11.1.515

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

## Sources

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

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