OS Command Injection in agentic-flow (CVE-2026-58195)
Summary
OS command injection in agentic-flow (CVE-2026-58195). Successful exploitation can lead to full system takeover. Exploitable via agent. Mitigation: upgrade to 2.0.14 or later.
Original description
The description as published by the source.
Agentic-Flow is an AI agent orchestration platform. Prior to 2.0.14, agentic-flow MCP server tools in src/mcp/standalone-stdio.ts, src/mcp/fastmcp/servers/claude-flow-sdk.ts, src/mcp/fastmcp/servers/stdio-full.ts, src/mcp/fastmcp/servers/http-streaming-updated.ts, src/mcp/fastmcp/servers/http-sse.ts, src/mcp/fastmcp/servers/poc-stdio.ts, src/mcp/fastmcp/tools/agent/{execute,list,parallel}.ts, src/mcp/fastmcp/tools/swarm/orchestrate.ts, and src/mcp/fastmcp/tools/hooks/pretrain.ts interpolated attacker-influenceable tool parameters such as agent, task, name, language, and agentdb directly into shell command strings passed to execSync(), allowing arbitrary OS command execution with the privileges of the MCP server user. This issue is fixed in version 2.0.14.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-58195 has been found in agentic-flow.
Attackers can target a specific entry point like agent over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade agentic-flow to 2.0.14 or later.
If unsure, ask your IT team or search "agentic-flow CVE-2026-58195" on the vendor's site.
CVE-2026-58195 (agentic-flow) — CWE-78 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: agent / task / name / language
Patched: 2.0.14 — apply immediately
Workaround: Upgrade to agentic-flow >= 2.0.14.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in agentic-flow. Attackers reach the vulnerable code path via agent without authentication.
Check the vendor advisory for the affected versions of agentic-flow. Attack surface: agent / task / name / language.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2.0.14.
Workaround: Upgrade to agentic-flow >= 2.0.14.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'agentic-flow' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'agentic-flow' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
agentic-flowを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Upgrade to `agentic-flow >= 2.0.14`.パッチが適用されるまでの応急処置として、Upgrade to
agentic-flow >= 2.0.14. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade agentic-flow to 2.0.14ステージング環境で 2.0.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- patch github.com
- report github.com
- report github.com
- web github.com
- web npmjs.com