# CVE-2026-129122: C-Kermit 6.0.192 before 11.1.515 Buffer Overflow via Telnet NEW-ENVIRON Negotiation


- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/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-129122, GHSA-3mg2-x3p2-9ccr, UBUNTU-CVE-2026-129122

## What is CVE-2026-129122?

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

### Official description

C-Kermit 6.0.192 before 11.1.515 contains a buffer overflow vulnerability in tn_snenv() in ckctel.c that allows malicious Telnet servers to corrupt client memory via crafted NEW-ENVIRON SEND subnegotiation. Malicious or machine-in-the-middle servers can send oversized variable names before authentication, overflowing a 16-byte stack buffer and a miscomputed heap buffer to corrupt stack and heap memory.

Weakness: CWE-787 (Out-of-bounds Write)

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

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 6.0.192 | 11.1.515 |

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

Upgrade openkermit/ckermit to 11.1.515 or later.

## Is CVE-2026-129122 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- openkermit/ckermit (GitHub): affected from 6.0.192; 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-129122/ (Markdown: https://insights.sbomify.com/CVE-2026-129122/index.md)
```

## Sources

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

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