cve.bz

CVE-2026-78136 Eval Injection

7.8 highEPSS 0.2%

High (7.8). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

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

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-08-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-95 Improper Neutralization of Directives in Dynamically Evaluated Code (Eval Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-78136 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-78136?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-78136?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-78136 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 16.0chirp20260911-bp160.1.1openSUSE-SU-2026:21866-1
openSUSETumbleweedchirp20260911-1.1openSUSE-SU-2026:11770-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's 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.

Red Hat's 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.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-78136.

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON