Case · DiggingBeagle record

AgentScope treated the file-writing tee command as safe without human approval

The AgentScope Bash-tool safety classifier treated tee as a safe command even though it writes files and short-circuited before destination-path danger checks. CVE-2026-123023 documents policy bypass for write effects without required human approval, with 2.0.9 identified as fixed.

Public disclosure: Nov 5, 2026

Scope

Reported security vulnerability; exploitation prerequisites and tested version scope matter. No real-world exploitation is established unless separately reported.

Assessment profile

Assessment method
Setting
research demonstration
Exploitation
demonstrated
Evidence
Grade C
Remediation
patch available
AI role
AGAINST AI
Basis and provenance

research demonstration; demonstrated. The cited primary disclosure supports the specific sequence and boundaries described here: Agent or operator invokes Bash-tool execution with tee in the command. The evidence does not independently establish consequences beyond the record's supported outcome; a numerical impact band cannot be justified from the available evidence. Evidence grade C reflects the source attribution and independent verification limits.

Assessed Nov 7, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    Agent or operator invokes Bash-tool execution with tee in the command.

  2. 02

    SAFE_COMMANDS classification returns without checking a write destination or requesting the intended approval.

  3. 03

    The shell writes to a path permitted by the underlying service account even when policy intended that write to be reviewed.

Claims & evidence

CLM-DB07-018-OUTCOMECVE-2026-123023 documents policy bypass for write effects without required human approval, with 2.0.9 identified as fixed. The effects remain limited by the tool process filesystem permissions.supported

Basis: reported finding

Link to claim
CLM-DB07-018-MECHANISMThe AgentScope Bash-tool safety classifier treated tee as a safe command even though it writes files and short-circuited before destination-path danger checks.supported

Basis: reported finding

Link to claim

Implications

Classify side effects rather than executable names and enforce protected-path checks even after an apparently safe verb.

Unknowns and contradictions

  • Tool must be called; effect limited by process filesystem privileges; no real exploit known.

Sources and citation

Material revision history

  1. Nov 7, 2026 · Canonical change recorded · new in release · revision 227