ACVERogue and malicious agent events

ACVE-2026-0502 · Real incident · HIGH

Unverified · secondary sources only

WHAT HAPPENED

The agent relocates every file into a destination that was never created, overwriting them under one name.

THE SETUP — is yours like this?

WHAT TO CHANGE

Confirm file relocation in unsandboxed sessions; verify the destination exists first.

  • Reconfigure agent.approval to ask. The relocation ran without a person checking the destination. Owner: operator
  • Reconfigure google.gemini-cli.shell to confirmation before moving or deleting files when no sandbox is on. Recommended: unconfirmed moves into a folder that was never created overwrote every file. Owner: harness-vendor

HARM, REACH AND RECOVERY

SOURCES

REPORT

EVIDENCE

Technical details

Destroyed a project's files by relocating them into a destination folder it had reported creating but that never existed: Gemini CLI 0.1.13, asked to rename a folder and relocate its files.

Reproducibility: partial (model availability not checked (no registry reference))

Claims

Confirmed means the statement matches the cited primary source. Nothing on this page has been reproduced.

ClaimStatusSourceChecked
Latest affected version 0.1.13 is still installable from npmConfirmedregistry.npmjs.org2026-09-22

Description

Threat

user · unsafe-default · file-write

What

The operator asked the agent to rename a project folder and relocate all its files into a new one. The command to create the destination folder returned success but never created it. The agent then relocated the files into that nonexistent destination, so each file overwrote the previous one under a single name and the contents were lost. The agent's own post-mortem in the transcript acknowledged the sequence.

Detection

The lockfile records the Gemini CLI version; the issue reports version 0.1.13, model gemini-2.5-pro, no sandbox. Recorded from the operator's issue and attached transcript. Not recreated in a lab.

Fix

Verify that a destination exists before relocating files into it, and keep file operations behind confirmation in unsandboxed sessions.

Report a problemJSON