AAK-AGENTSCOPE-CVE-2026-123023-001: AgentScope 2.0.0 to 2.0.8: the Bash tool counts tee as read-only, so an agent writes files without asking
- Severity
- HIGH
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
AgentScopeBashTeeReadOnly
What it detects
AgentScope (PyPI agentscope, agentscope-ai/agentscope) 2.x gives every workspace's agents a built-in Bash tool. Its check_permissions allows a command its parser calls read-only at once, ahead of the tool's dangerous-command and dangerous-path checks, and the parser's SAFE_COMMANDS set, which makes that call, listed tee through 2.0.8. tee writes the files it is given, so a command that pipes into it writes or appends to any file the agent's user can write, where the same write through > asks first. Whoever steers the agent, through prompt injection or the 2.x service's API, can add a login key or change a shell startup file (CVE-2026-123023, CVSS 3.1 7.3, CWE-863). Checked in the PyPI wheels: 1.0.21, the last 1.x release, has no Bash tool; every release from 2.0.0 (2026-05-25) to 2.0.8, 2.0.4.post1 and 2.0.7.post1 included, lists tee; 2.0.9 (2026-09-28) removes it (agentscope-ai/agentscope#2629, commit 6b43b13), and 2.0.10 and 2.0.11 leave it out.
How to fix
Upgrade agentscope to 2.0.9 or later and pin it. Until you can, run agents that read input you do not control in a Docker or E2B workspace, where a write through tee stays inside the sandbox, and keep a 2.x service's API off networks you do not trust.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-AGENTSCOPE-CVE-2026-123023-001
Limitations
Reports a PyPI reference to agentscope from 2.0.0 below 2.0.9 that states a version: a requirements*.txt entry at any depth, a pyproject.toml, Pipfile or lockfile entry at the project root, or the package a uvx launch in an MCP config names, judging a range by the versions it admits. latest is 2.0.11, fixed, so a reference that states no version is not reported. 2.0.4.post1 and 2.0.7.post1 read as 2.0.4 and 2.0.7, both affected. It reads the version, not whether the project gives an agent the Bash tool or which permission mode it runs, so a project that uses AgentScope without the tool is reported too. 1.x releases have no Bash tool and are not reported. npm's agentscope is another project and is not matched. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.
References
- CVE: CVE-2026-123023
- OWASP Agentic Top 10: ASI02 (Tool Misuse and Exploitation), ASI09 (Human-Agent Trust Exploitation), ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-SUPPLY-04 (Known Vulnerable Dep)
- CSA AI Controls Matrix (AICM): AIS-07, STA-08
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-AGENTSCOPE-CVE-2026-123023-001.md: the page then shows that text, with the registry reference appended under it.