CVE-2026-78136

Description

A flaw was found in CHIRP from chirpmyradio. A local attacker can achieve arbitrary code execution by tricking a user into processing a specially crafted Comma Separated Values (CSV) file. This vulnerability, an eval injection, occurs within the _clean_tmode function when handling CSV data, leading to high impacts on confidentiality, integrity, and availability.

Statement

This vulnerability is rated as Important severity for Red Hat product security because successful exploitation allows arbitrary code execution within the context of the running user session. CHIRP is an amateur radio programming tool that is not shipped or supported in Red Hat Enterprise Linux, restricting exposure to community environments where users manually install the package. Because triggering the flaw requires direct user interaction to process an untrusted input file rather than exposing a network service, the blast radius is strictly confined to the local user's privileges.

Mitigation

To mitigate this vulnerability, users should avoid importing or processing CSV files from untrusted sources with CHIRP. Exercise caution when handling CSV data, especially if its origin is unknown or suspicious.

Understanding the Weakness (CWE)

Access Control

Technical Impact: Bypass Protection Mechanism

In some cases, injectable code controls authentication; this may lead to a remote vulnerability.

Access Control

Technical Impact: Gain Privileges or Assume Identity

Injected code can access resources that the attacker is directly prevented from accessing.

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

When a product allows a user's input to contain code syntax, it might be possible for an attacker to craft the code in such a way that it will alter the intended control flow of the product. As a result, code injection can often result in the execution of arbitrary code. Code injection attacks can also lead to loss of data integrity in nearly all cases, since the control-plane data injected is always incidental to data recall or writing.

Non-Repudiation

Technical Impact: Hide Activities

Often the actions performed by injected control code are unlogged.

Frequently Asked Questions

Want to get errata notifications? Sign up here.