chirpmyradio CHIRP before 39178db allows eval injection via crafted CSV data. This occurs in _clean_tmode in drivers/kenwood_itm.py.
CVE-2026-78136
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(low)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 23, 2026
Last Modified
August 23, 2026
Advisory Details (2)
Auto-updated Aug 23, 2026commit 39178dbfc4fe (kk7ds/chirp)
Fix landed in kk7ds/chirp commit 39178dbfc4fe — awaiting tagged release
https://github.com/kk7ds/chirp/commit/39178dbfc4fece083ab9ed20286d6ae3a91a718eGitHub - cduram/CHIRP-CodeExecution_via_Malicious_ImageFile: Arbitrary Code Execution via eval() in Kenwood ITM Driver · GitHub
https://github.com/cduram/CHIRP-CodeExecution_via_Malicious_ImageFileVendor Advisories for CVE-2026-78136(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-23 01:27 UTCEG score recompute
- 2026-08-23 01:02 UTCEG score recompute
- 2026-08-23 01:01 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-95
- CVE-2025-54322EG 10.0EPSS p96CRITICAL
- CVE-2025-55728EG 10.0CRITICAL
- CVE-2025-55727EG 10.0CRITICAL
- CVE-2013-10070EG 10.0CRITICAL
- CVE-2024-31996EG 10.0CRITICAL
- CVE-2024-31982EG 10.0EPSS p98CRITICAL
- CVE-2023-26477EG 10.0EPSS p99CRITICAL
- CVE-2022-36010EG 10.0CRITICAL
- CVE-2021-23277NVD 8.3EG 10.0CRITICAL
- CVE-2025-49013EG 9.9CRITICAL
Frequently asked(4)
What is CVE-2026-78136?
When was CVE-2026-78136 disclosed?
What is the CVSS score of CVE-2026-78136?
How do I remediate CVE-2026-78136?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78136
Is Your Infrastructure Affected by CVE-2026-78136?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.