3D isometric illustration of a cracked sandbox container with code brackets leaking out, representing sandbox vulnerabilities in Claude Code, Cursor, and Codex
💜 Software · AI Coding Tools

Claude Code’s Sandbox Bug Took 50 Days to Fix

A stealth security startup flagged leaky sandboxes in Claude Code, Cursor, and Codex, and the three vendors did not respond at the same speed

📅 September 2026 ⏱ 6 min read
Accomplish flagged bugs in three major coding tools
Cursor and OpenAI patched in about a week
Anthropic took 50 days and 30 releases
Cursor
Fix Turnaround
~7 Days
OpenAI
Two Bugs Fixed
~7 Days
Anthropic
Releases Before Patch
30

Three of the most widely used AI coding tools quietly had leaky sandboxes this summer, and how fast each vendor fixed them looked nothing alike. A Tel Aviv-based stealth security startup called Accomplish, founded by Or Hiltch, Amit Avner, and Guy Zipori, privately flagged sandbox vulnerabilities to Anthropic, Cursor, and OpenAI earlier this year, then went public with the findings this week. Accomplish’s CTO, Hiltch, put it plainly: “There’s a lot of talk about security now.”

A sandbox is the isolated environment meant to stop a coding agent from touching the rest of a developer’s machine or a company’s data while it works. Accomplish’s own writeup names its Claude Code finding “Beltdown,” and it lands in a pattern security researchers have documented repeatedly in 2026, including a “Configuration-Based Sandbox Escape” class flagged across Claude Code, Codex, and Gemini CLI in the spring, and a related set of vulnerabilities across Cursor, Codex, Gemini CLI, and Antigravity reported over the summer.

What set this disclosure apart was the response gap. A bug Accomplish flagged to Cursor in July, and two flagged to OpenAI, were each fixed in about a week. A similar issue flagged to Anthropic roughly two months earlier took about 50 days and around 30 separate software releases before a patch shipped. Anthropic and Cursor did not respond on the record to requests for comment; OpenAI said it addressed both of its flagged issues in August and is continuing to tighten controls on where its agents can write files.

📊 The Disclosure at a Glance
What Happened

Three Tools, Three Timelines

Accomplish flagged sandbox bugs in Claude Code, Cursor, and Codex; Cursor and OpenAI moved in about a week, Anthropic took 50 days.

Why It Matters

Sandboxes Are the Trust Boundary

A coding agent’s sandbox is what is supposed to keep it from touching the rest of a developer’s machine or company data.

The Pattern

This Keeps Happening

Separate researchers have flagged similar sandbox-escape vulnerability classes in these same tools at least three times so far in 2026.

What’s Next

Response Time, Not Just Claims

Accomplish says it wants the industry talking about how fast vendors actually fix these issues, not just their security messaging.

What Accomplish Actually Found
01

Beltdown, the Claude Code Finding

Disclosure

Accomplish published its own technical writeup describing a way to escape Claude Code’s sandbox, which it nicknamed Beltdown. The startup flagged it to Anthropic privately roughly two months before going public with the research this week.

💡 Why it matters. A sandbox escape means code the agent runs could reach files or systems outside the isolated environment it was supposed to be confined to.
02

The Response Time Gap

Vendor Response

Cursor patched a bug flagged in July within about a week. OpenAI fixed two separately reported issues on a similar timeline and says both were resolved by August. Anthropic’s fix for a comparable Claude Code issue took roughly 50 days and about 30 software releases.

💡 Accomplish’s take. CEO Amit Avner says the gap matters because a flagged but unpatched vulnerability stays exploitable by anyone else who finds it independently.
03

Not a One-Off Pattern

Bigger Picture

This is at least the third documented sandbox-escape pattern across popular AI coding tools in 2026. Earlier researchers flagged a “Configuration-Based Sandbox Escape” class in Claude Code, Codex, and Gemini CLI, and a separate report covered Cursor, Codex, Gemini CLI, and Antigravity over the summer.

💡 Common thread. Most of these issues exploit files the agent writes inside the sandbox that a trusted tool later runs outside it, rather than breaking the sandbox directly.
04

What Developers Should Do

Practical Steps

Keep coding agents updated to their latest versions, since most disclosed issues in this pattern have shipped fixes. Be cautious running any agent against an untrusted or third-party repository, and check for unusual .git configuration files before opening one with an agent enabled.

💡 Where to check. Vendor changelogs and security advisories for Claude Code, Cursor, and Codex are the fastest way to confirm whether a specific fix has shipped for your version.

Organizations need
to be very wary

Amit Avner, Accomplish · September 2026

⚠️ Before You Assume Your Setup Is Fine

1. A public disclosure doesn’t mean a public exploit. No source in this reporting confirmed these specific vulnerabilities were actively exploited before being patched.

2. Two vendors didn’t comment on the record. Anthropic and Cursor did not respond to on-record requests for comment on Accomplish’s findings, so their side of the response timeline is incomplete here.

3. This is a pattern, not a single bug. Similar sandbox-escape classes have been reported in these tools multiple times in 2026, so one patch does not necessarily close the broader issue.

✅ The Verdict

The Sandbox Disclosure, What Actually Matters

1
Accomplish privately flagged sandbox bugs in Claude Code, Cursor, and Codex earlier this year
2
Cursor and OpenAI each patched their flagged issues in about a week
3
Anthropic’s fix for a similar Claude Code issue took about 50 days and 30 releases
4
This is at least the third documented sandbox-escape pattern in these tools this year
5
Keeping agents updated and checking untrusted repos remains the most direct protection right now
🔗 Read Accomplish’s own Beltdown technical writeup for the full vulnerability details.
💬 Frequently Asked Questions
Q. What is a sandbox escape in an AI coding tool?
It is a way for code or files the AI agent produces inside its isolated sandbox to end up run or trusted outside that boundary, potentially reaching the rest of a developer’s machine or company data.
Q. Which AI coding tools were affected this time?
Accomplish’s disclosure covered Claude Code, Cursor, and OpenAI’s Codex. Earlier reports in 2026 documented related issues in Gemini CLI and Antigravity as well.
Q. How long did each vendor take to fix the issues?
Cursor and OpenAI each patched their flagged issues in about a week. Anthropic’s fix for a similar Claude Code issue took roughly 50 days and about 30 separate software releases.
Q. Is it safe to keep using Claude Code, Cursor, or Codex?
The specific issues Accomplish reported have been patched, according to available statements. Keeping the tools updated and being cautious with untrusted repositories remains the most direct way to reduce risk from this vulnerability class.
Editor’s Note. This article draws on Upstarts Media’s September 10, 2026 reporting on Accomplish’s disclosure, Accomplish’s own technical writeup, and earlier 2026 sandbox-escape research from Cymulate, Pillar Security, and independent researchers.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top