CVE-2026-108817 agno-agi CVE debrief

Who should care

Defenders responsible for agno-agi agno deployments should assess exposure and prioritize upgrading to version 3.0.10. They should also verify exposure through inventory checks, review compensating controls, and monitor for potential exploitation attempts. Security teams and vulnerability management teams should track exceptions and retest remediated assets.

Why it matters

Defenders should care about CVE-2026-108817 because it allows for os command injection in agno-agi agno deployments, potentially enabling remote attacks. Exposure verification, upgrade prioritization, and monitoring are necessary.

• Verify exposure through inventory checks
• Prioritize upgrading to version 3.0.10
• Monitor for potential exploitation attempts

Technical summary

The function agno.CodingTools.run_shell in the library libs/agno/agno/tools/coding.py of the component CodingTools is vulnerable to os command injection. The attack may be initiated remotely. Defenders should prioritize upgrading to version 3.0.10 and perform inventory checks to verify exposure. Monitoring and exception tracking may be required to detect potential exploitation attempts. The vulnerability allows for os command injection, potentially enabling remote attacks on agno-agi agno deployments. Exposure verification and upgrade prioritization are necessary.

Defensive priority

Defenders should prioritize upgrading to version 3.0.10. Inventory checks are necessary to verify exposure. Monitoring and exception tracking may be required.

Recommended defensive actions

• Upgrade to version 3.0.10
• Inventory checks to verify exposure
• Monitoring and exception tracking
• Review compensating controls for exposed systems
• Check relevant monitoring, detection, and logs for exposed assets
• Track exceptions and retest remediated assets
• Confirm whether affected product deployments exist in managed environments

Evidence notes

The CVE record and source item provide details on the vulnerability. However, the scope of affected versions and potential impact require verification from official sources. Defenders should verify exposure through inventory checks and review compensating controls. The CVE Program record (cve-org) and NIST NVD detail page (nvd) offer source-grounded information. Supplemental sources (ref-4, ref-5) provide additional context.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.