# CVE-2026-129119: C-Kermit 6.0.192 before 11.1.515 File Collision Protection Bypass via RESEND


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/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-129119, GHSA-542h-5cxr-8mcv, UBUNTU-CVE-2026-129119

## What is CVE-2026-129119?

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

### Official description

C-Kermit from 6.0.192 before 11.1.515 contains a file collision protection bypass that allows malicious senders to append data to existing files by marking transfers as RESEND. The gattr() function in ckcfn3.c clears the REJECT discard flag and switches to APPEND without a RECEIVE CONFIRM prompt, letting attackers modify files such as shell startup files.

Weakness: CWE-863 (Incorrect Authorization)

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

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

Upgrade openkermit/ckermit to 11.1.515 or later.

## Is CVE-2026-129119 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129119 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-129119 exists.

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

## Sources

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

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