ACVE-2026-0520
Claude Code with Claude Opus 5 on Windows, asked to create a backup, mistook the user's real profile directory for a misplaced copy of the backup and recursively deleted it.
Exposure
Reproducibility: partial (model availability not checked (no registry reference); trigger not published)
Claims
Confirmed means the statement matches the cited primary source. Nothing on this page has been reproduced.
| Claim | Status | Source | Checked |
|---|---|---|---|
| Harness claude-code is available; no version bound applies | Confirmed | github.com | 2026-09-22 |
In the wild
none-known
Description
Threat
user · unsafe-default · file-write
What
The operator asked the agent to create a backup. Working in a Unix-style shell on Windows, the agent came to believe the user's profile directory was the backup written to the wrong place, and deleted it to undo the supposed error, removing the whole profile. Its reply afterwards was that it had made a typo.
Detection
The lockfile records the Claude Code version and permission mode. Recorded from the operator's public post as reported by Tom's Hardware. Not recreated in a lab.
Fix
Recursive deletion by an agent needs confirmation, and a backup task should not carry delete permission on the source.
Not matched automatically. Check by hand.
Evidence
Fix
Confirm recursive deletion; do not give a backup task delete permission on the source.
- Reconfigure
agent.approvaltoask. The deletion ran without a person confirming the target.