THE PERMISSION [LAYER]

AI agent incident

A DeepSeek Harness flaw let an agent switch off its own file sandbox

Reported · 1 source

What happened

A flaw in DeepSeek Harness let a sandboxed coding agent call its own tool API to disable the file sandbox, with no approval step in the way.

Why it matters

A sandbox the agent can turn off from inside is a setting, not a boundary. The control has to sit somewhere the agent's tool surface cannot reach.

Sources

  1. The Hacker News DeepSeek Harness Flaw Let AI Agents Disable Their Own File Sandbox Without Approval

New incidents by email

Get incidents like this one in your inbox

New AI agent incidents are covered in the briefing, with what to check on the agents you already run. At least once a week, free.

You confirm by email. Unsubscribe in one click.

Background reading

Does RBAC work for AI agents? An explainer on the problem behind this incident.

Cite or correct this record

“A DeepSeek Harness flaw let an agent switch off its own file sandbox.” The Permission Layer AI Agent Incident Database, https://thepermissionlayer.com/incidents/deepseek-harness-sandbox-disable/. Database updated October 22, 2026.

Every record traces to the dated sources above. If something here is wrong or missing, email [email protected] and it gets fixed. See this record in the full list.

The Permission Layer

Get the briefing by email

At least one email a week on AI agent identity, permissions, security and spend, written for the people who approve agent access. Five-minute read, free.

You confirm by email. Unsubscribe in one click.