Post

I have questions: what is this sandbox exploit? Why wasn’t this lab airgapped or close to airgapped. In AWS this would be a VPC with no internet router/no NAT gateway. So what was that the sandbox they escaped from? In short: either they massively under sandboxed or the exploit is *really* serious.

As far as I can tell their sandbox was a container with network access denied except for a single IP for an HTTP proxy that controlled which sites could be accessed, and the proxy turned out to have a flaw I wrote about their production version of that back in Jan: simonwillison.net/2026/Jan/26/...

simonwillison.netChatGPT Containers can now run bash, pip/npm install packages, and download filesOne of my favourite features of ChatGPT is its ability to write and execute code in a container. This feature launched as ChatGPT Code Interpreter nearly three years ago, was …

0 reposts3 likes

Thanks. In hindsight obviously not a stringent enough sandbox. But also unclear what sort of behaviours they were trying/expecting to elicit (ie. what risk did they think it was) Interesting for sure. Can’t quite make up my mind how concerning it is. I imagine (hope?) lessons are being learnt.