A vulnerability was determined in agno-agi agno up to 3.0.9. Affected by this issue is the function agno.CodingTools.run_shell in the library libs/agno/agno/tools/coding.py of the component CodingTools. This manipulation of the argument command causes os command injection. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 3.0.10 can resolve this issue. Patch name: ed64fab5be63d2b15faddc2ef7c733176daa14aa. You should upgrade the affected component.
CVE-2026-108817
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.5 from GitHub Security Advisory (severity: LOW) published 2026-10-12. A secondary CVSS source baseline 5.5; sources differ by 0.0.
Also known asEUVD-2026-97301 (ENISA EUVD) · GHSA-gfx7-4mpr-25fj (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 5.5
- EG Score
- 5.5MEDIUMhigh confidence
- EG Risk
- 41EG Risk 41/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity55% × 45%Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 1.1%
- EPSS %ILE
- 64th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 1.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 12, 2026
Last Modified
October 13, 2026
Advisory Details (5)
Auto-updated Oct 12, 2026v3.0.10
Patch available: agno-agi/agno v3.0.10
https://github.com/agno-agi/agno/releases/tag/v3.0.10commit ed64fab5be63 (agno-agi/agno)
Patch available: agno-agi/agno v3.0.10 (contains commit ed64fab5be63)
https://github.com/agno-agi/agno/commit/ed64fab5be63d2b15faddc2ef7c733176daa14aaagno-security-advisories/advisories/agno-codingtools-run-shell-disallowlist-bypass-command-execution.md at main · ybyu-ieu/agno-security-advisories · GitHub
https://github.com/ybyu-ieu/agno-security-advisories/blob/main/advisories/agno-codingtools-run-shell-disallowlist-bypass-command-execution.mdfix: harden CodingTools run_shell against interpreter RCE
Patch available: agno-agi/agno v3.0.10 (PR #10210 merged 2026-09-16)
https://github.com/agno-agi/agno/pull/10210[Bug] CodingTools run_shell allows arbitrary command execution via chr()-encoding bypass of the restricted-mode command disallowlist (CWE-78, CVSS 9.8) · Issue #10048 · agno-agi/agno · GitHub
https://github.com/Agno-agi/Agno/issues/10048Vendor Advisories for CVE-2026-108817(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 9× in last 7d / 38× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-02 16:43 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-31 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-29 15:00 UTCEG score recompute
- 2026-10-29 15:00 UTCGHSA enrichmentGHSA-gfx7-4mpr-25fj · GitHub severity LOW · GitHub CVSS 5.5
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-25 14:53 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-23 08:26 UTCEG score recompute
- 2026-10-23 08:25 UTCGHSA enrichmentGHSA-gfx7-4mpr-25fj · GitHub severity LOW · GitHub CVSS 5.5
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-20 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-18 05:07 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.1% · 64th percentile
Show 13 moreShow fewer
- 2026-10-14 16:32 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-13 19:51 UTCEG score recompute
- 2026-10-13 19:50 UTCGHSA enrichmentGHSA-gfx7-4mpr-25fj · GitHub severity LOW · GitHub CVSS 5.5
- 2026-10-13 19:24 UTCNVD updateCVSS v4 → 2
- 2026-10-13 18:53 UTCEG score recompute
- 2026-10-13 18:52 UTCGHSA enrichmentGHSA-gfx7-4mpr-25fj · GitHub severity LOW · GitHub CVSS 5.5
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-12 16:38 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 1.1% · 64th percentile
- 2026-10-12 09:26 UTCEG score recompute
- 2026-10-12 09:24 UTCNVD updateCVSS v4 → 2
- 2026-10-12 08:47 UTCEG score recomputeFirst assessed: 5.5 MEDIUM
- 2026-10-12 08:47 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78 · CWE-77
Frequently asked(5)
What is CVE-2026-108817?
When was the CVE record for CVE-2026-108817 published?
Is CVE-2026-108817 actively exploited?
What is the CVSS score of CVE-2026-108817?
How do I remediate CVE-2026-108817?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108817
Is Your Infrastructure Affected by CVE-2026-108817?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.