CVE-2025-68920 json
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 s…
published 2025-12-24 10 mo ago modified 2026-10-07 33 d ago also EUVD-2025-205357
- cvss
- 8.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- ckermit Debian 13 416~beta12-1+deb13u1
- ckermit Debian 14 416~beta12-5
debian advisories DEBIAN-CVE-2025-68920
- ckermit openSUSE Tumbleweed 9.0.302-20.1
opensuse advisories openSUSE-SU-2026:10495-1
- github.com/KermitProject/ckermit#20 pull request
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-68920 updated cvss 9.1
cKermit: From CVEorg collector
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 10 mo ago
Exploit prediction
0.44% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L |
Affected products
- kermitproject C-Kermit
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
Sources
- CVE List CVE-2025-68920
- NVD CVE-2025-68920
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.