A vulnerability was found in louisho5 picobot up to 0.2.0. This issue affects the function ExecTool.Execute of the file internal/agent/tools/exec.go of the component exec Tool. The manipulation results in os command injection. The attack requires a local approach. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.
CVE-2026-15669
This medium-severity CVE scores 5.3 under the CNA's CVSS (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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(low)
- EPSS
- —
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 14, 2026
Advisory Details (3)
Auto-updated Jul 14, 2026GitHub - louisho5/picobot: A lightweight self-hosted bot in a single binary, written in Go. · GitHub
https://github.com/louisho5/picobot/[Security] Picobot `exec` tool dangerous-program blacklist bypass via `env` and `bash -lc` dispatch · Issue #43 · louisho5/picobot · GitHub
https://github.com/louisho5/picobot/issues/43[Security] Picobot `exec` tool shell-wrapper bypass allows arbitrary command execution · Issue #42 · louisho5/picobot · GitHub
https://github.com/louisho5/picobot/issues/42Vendor Advisories for CVE-2026-15669(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× 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-07-14 13:19 UTCNVD updateCVSS v4 → 1.9
- 2026-07-14 13:11 UTCMITRE cvelistV5CVSS v4 → 4.8
- 2026-07-14 07:16 UTCNVD updateCVSS v4 → 1.9
- 2026-07-14 05:20 UTCEG score recompute
- 2026-07-14 05:20 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78 · CWE-77
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2011-10026EG 9.8CRITICAL
- CVE-2011-2195EG 9.8CRITICAL
- CVE-2011-2523EG 9.8EPSS 100%CRITICAL
- CVE-2010-5330EG 9.8 KEVEPSS 98%CRITICAL
- CVE-2009-5156EG 9.8EPSS 95%CRITICAL
- CVE-2007-3010EG 9.8 KEVEPSS 100%CRITICAL
- CVE-2005-2773EG 9.8 KEVEPSS 99%CRITICAL
- CVE-1999-0043EG 9.8EPSS 99%CRITICAL
Frequently asked(4)
What is CVE-2026-15669?
When was CVE-2026-15669 disclosed?
What is the CVSS score of CVE-2026-15669?
How do I remediate CVE-2026-15669?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15669
Is Your Infrastructure Affected by CVE-2026-15669?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.