# CVE-2025-68920: Path traversal in C-Kermit

> A remote attacker can overwrite or retrieve arbitrary files on the local system via the Kermit protocol.

- **Severity:** High 8.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 24 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-68920, GHSA-7wwf-6mwx-wx77, UBUNTU-CVE-2025-68920, openSUSE-SU-2026:10495-1

## What is CVE-2025-68920?

CVE-2025-68920 is a high-severity path traversal vulnerability in kermitproject C-Kermit, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

C-Kermit (aka ckermit) through 10.0 Beta.12 (aka 416-beta12) before 244644d allows a remote Kermit system to overwrite files on the local system, or retrieve arbitrary files from the local system.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-68920?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ckermit` | openSUSE:Tumbleweed | All versions | 9.0.302-20.1 |

## How do I fix CVE-2025-68920?

Apply the vendor's patch.

## Is CVE-2025-68920 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68920 and fix it if it is affected.

What it is: CVE-2025-68920 is a high-severity path traversal vulnerability in kermitproject C-Kermit, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68920 in the wild and no public exploit code.

Affected product: kermitproject C-Kermit. 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-2025-68920/ (Markdown: https://insights.sbomify.com/CVE-2025-68920/index.md)
```

## Sources

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

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