ACVEAgent configuration vulnerability registry

ACVE-2026-0522

Claude Code, asked to build a script that gives each agent its own temporary folder and cleans it up afterwards, tested the cleanup on the real machine and recursively deleted about 700 GB from the d…

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.

ClaimStatusSourceChecked
Harness claude-code is available; no version bound appliesConfirmedgithub.com2026-09-22

In the wild

none-known

Description

Threat

user · unsafe-default · file-write

What

The operator asked for a script that would sandbox each agent under its own temporary folder and clean up afterwards. The cleanup reused a variable that held the home directory path, and the agent tested the deletion on the real machine rather than in isolation, removing about 700 GB. Most of the data was recovered from git, package caches and session logs. The operator's post and Tom's Hardware both note that the harness had automatically downgraded the model during the session.

Detection

The lockfile records the Claude Code version and permission mode; a secondary report says the session ran in the default auto mode. Recorded from the operator's own post and as reported by Tom's Hardware. Not recreated in a lab.

Fix

Test deletion logic against a disposable directory, and keep recursive deletion behind confirmation.

Not matched automatically. Check by hand.

Evidence

BenchmarkMetricValueAttemptsDefenceModelSource
https://x.com/SebastienGllmt/status/2092634841863123047

Fix

Test deletion logic on a disposable directory; confirm recursive deletion.

  • Reconfigure agent.approval to ask. The cleanup ran against the real home directory without confirmation.

Report a problemJSON