CVE-2026-129125 in C-Kermit
Summary
by MITRE • 11/13/2026
C-Kermit 6.0.192 before 11.1.515 contains a remote code execution vulnerability that allows Kermit clients to run shell commands on servers with host commands disabled by abusing REMOTE QUERY evaluation. Attackers can send a REMOTE QUERY invoking the command function, or define a macro via REMOTE ASSIGN and call execute to reach RUN, bypassing the nopush restriction and DISABLE HOST.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/13/2026
The vulnerability identified in C-Kermit versions prior to 11.1.515 represents a critical remote code execution flaw rooted in the improper handling of command evaluation sequences within the Kermit protocol implementation. C-Kermit is a widely used file transfer and terminal emulation program, and its security model relies heavily on configuration settings that restrict user actions for safety and stability. Specifically, administrators often disable host commands to prevent clients from executing arbitrary system-level operations on the server side. However, this vulnerability allows an attacker to bypass these restrictions by exploiting how the software processes REMOTE QUERY and REMOTE ASSIGN directives during a session. The core technical flaw lies in the evaluation logic of the remote query mechanism, which fails to adequately sanitize or restrict the execution context when processing commands sent from a client to the server.
An attacker can leverage this weakness by crafting specific network packets that invoke the command function through a REMOTE QUERY directive. Alternatively, the attack vector involves defining a macro via REMOTE ASSIGN and subsequently calling an execute function that leads to RUN operations. This sequence effectively circumvents the nopush restriction and disables the protective measures intended by DISABLE HOST settings. By manipulating these internal evaluation states, the attacker gains the ability to inject and run shell commands on the vulnerable server with the privileges of the C-Kermit process. This bypass is particularly dangerous because it exploits legitimate protocol features in an unintended manner, making detection through standard signature-based methods difficult without deep packet inspection capabilities that understand Kermit-specific state machines.
The operational impact of this vulnerability is severe, as it results in full remote code execution on the target system. Since C-Kermit often runs with elevated privileges or access to sensitive file systems depending on its deployment context, an attacker can potentially take complete control of the affected server. This could lead to data exfiltration, installation of persistent backdoors, lateral movement within a network, or disruption of critical services. The ability to bypass host command restrictions means that security controls designed to limit user interaction with the operating system are rendered ineffective against this specific attack vector. Organizations relying on C-Kermit for legacy file transfers or terminal sessions face significant risk if they have not applied the necessary patches or implemented compensating controls such as network segmentation and strict access control lists limiting Kermit traffic to trusted sources only.
To mitigate this vulnerability, organizations must immediately upgrade C-Kermit to version 11.1.515 or later, where these evaluation flaws have been addressed by the developers. In environments where upgrading is not immediately feasible, it is crucial to restrict network access to C-Kermit services using firewalls and intrusion prevention systems that can filter Kermit protocol traffic based on source IP addresses rather than relying solely on application-level host command restrictions. Additionally, monitoring for anomalous Kermit sessions involving unusual macro definitions or remote query patterns can help detect potential exploitation attempts in real-time. This vulnerability is classified under CWE-94 as Improper Control of Generation of Code (Code Injection) and aligns with MITRE ATT&CK techniques related to Command and Scripting Interpreter abuse, specifically highlighting the risk of bypassing security restrictions through protocol-specific logic errors.