CVE-2026-129126 in C-Kermitinfo

Summary

by MITRE • 11/13/2026

C-Kermit before 11.1.515 contains a heap buffer overflow vulnerability in putsrv() in ckcfns.c that allows malicious peers to write past the srvcmd buffer by sending crafted packets. Attackers can use Kermit repeat-count compression in server command, GET, or file-header packets to write attacker-chosen bytes beyond the heap buffer on servers or receiving instances.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/13/2026

The vulnerability identified in C-Kermit versions prior to 11.1.515 represents a critical memory safety flaw located within the putsrv function of the ckcfns.c source file. This defect is classified as a heap-based buffer overflow, which occurs when a program writes data beyond the allocated boundaries of a buffer on the heap. In this specific instance, the root cause lies in the improper handling of Kermit repeat-count compression mechanisms during the processing of server commands, GET requests, and file-header packets. When C-Kermit operates as a server or receives incoming connections, it parses these compressed sequences to reconstruct data streams efficiently. However, due to insufficient validation of the calculated buffer sizes against the actual allocated memory regions, an attacker can craft maliciously formatted packets that exploit this miscalculation. By manipulating the repeat-count fields within the Kermit protocol headers, a remote adversary can force the application to write arbitrary bytes past the end of the srvcmd buffer into adjacent heap memory locations.

From a technical perspective, this vulnerability falls under CWE-122, which denotes a heap-based buffer overflow allowing for out-of-bounds writes. The exploitation vector is particularly dangerous because it does not require local access or authentication in many default configurations where C-Kermit listens on open ports. An attacker positioned remotely can send specially crafted packets that trigger the overflow condition during the parsing phase of the Kermit protocol implementation. Because the write operation targets heap memory, the consequences extend beyond simple data corruption. The ability to overwrite adjacent heap metadata or function pointers enables an attacker to achieve arbitrary code execution with the privileges of the process running C-Kermit. This aligns with ATT&CK technique T1203, which covers exploitation for client-side execution if targeting a user interface, but more accurately reflects server-side remote code execution patterns where malicious input is processed by a service daemon.

The operational impact of this vulnerability is severe, potentially leading to complete system compromise. If an attacker successfully exploits the heap buffer overflow, they can inject and execute shellcode or other malicious payloads within the context of the vulnerable process. This could result in unauthorized access to sensitive files stored on the server, modification of critical configuration data, or use of the compromised host as a pivot point for further attacks within the network infrastructure. Additionally, depending on how the heap allocator handles corrupted metadata, this flaw might also lead to denial-of-service conditions through application crashes or memory corruption that destabilizes other processes sharing the same address space. The lack of bounds checking in the compression decompression logic means that even seemingly benign file transfers can serve as a delivery mechanism for exploitation if the sender controls the packet structure.

Mitigation strategies must prioritize immediate patching and network-level defenses. Organizations running C-Kermit should upgrade to version 11.1.515 or later, where this heap overflow has been remediated through proper input validation and bounds checking in the putsrv function. Until patches are applied, it is advisable to restrict access to Kermit services using firewall rules that limit connections to trusted IP addresses only. Furthermore, deploying intrusion detection systems capable of identifying anomalous patterns in Kermit protocol traffic can help detect attempted exploitation based on unusual repeat-count values or packet structures. Security teams should also audit their infrastructure for any instances where C-Kermit is exposed to untrusted networks and consider replacing it with more modern file transfer protocols that have undergone rigorous security auditing, such as SFTP or SCP, which do not suffer from these legacy protocol implementation flaws.

Responsible

VulnCheck

Reservation

11/13/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00604

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!