# CVE-2026-78136: Code injection in CHIRP

> Attackers can execute arbitrary code by providing crafted CSV data to CHIRP radio programming software.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-6rmm-3cfr-7939, MGASA-2026-0473, openSUSE-SU-2026:11770-1, openSUSE-SU-2026:21866-1

## What is CVE-2026-78136?

CVE-2026-78136 is a high-severity code injection vulnerability in chirpmyradio CHIRP, published on 23 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

chirpmyradio CHIRP before 39178db allows eval injection via crafted CSV data. This occurs in _clean_tmode in drivers/kenwood_itm.py.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

## Which versions are affected by CVE-2026-78136?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `chirp` | openSUSE:Leap 16.0 | All versions | 20260911-bp160.1.1 |
| `chirp` | openSUSE:Tumbleweed | All versions | 20260911-1.1 |

## How do I fix CVE-2026-78136?

Apply the vendor's patch.

## Is CVE-2026-78136 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-78136 and fix it if it is affected.

What it is: CVE-2026-78136 is a high-severity code injection vulnerability in chirpmyradio CHIRP, published on 23 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-78136 in the wild and no public exploit code.

Affected product: chirpmyradio CHIRP. 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-2026-78136/ (Markdown: https://insights.sbomify.com/CVE-2026-78136/index.md)
```

## Sources

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

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