# CVE-2026-129123: C-Kermit 8.0.200 before 11.1.515 FTP Client Buffer Overflow via PBSZ and ADAT Replies


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/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:** 13 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-129123, GHSA-f8jp-whmp-v2jf, UBUNTU-CVE-2026-129123

## What is CVE-2026-129123?

CVE-2026-129123 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 a buffer overflow vulnerability in getreply() in ckcftp.c that allows malicious FTP servers to overwrite client memory by sending overlong security replies. Attackers controlling or intercepting an FTP server can send long PBSZ replies after AUTH TLS, or long ADAT replies in GSSAPI, Kerberos 4, and SRP builds, overflowing the static reply_buf with attacker-controlled bytes.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

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-129123?

Upgrade openkermit/ckermit to 11.1.515 or later.

## Is CVE-2026-129123 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129123 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129123 is a high-severity vulnerability in OpenKermit C-Kermit, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-129123 exists.

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

## Sources

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

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