404 Media: Meta rushed to fix ‘KVM escape’ flaws in its Muse agent just before launch
Insiders expect ‘a massive data breach’
Partly confirmed
Status
- Claim
Partly confirmed
- Our reporting
- Medium confidence
- Importance
- 3 of 5
- Last verified
- 7 October 2026
Your AI and this story
- GPT-6.2 Astra127 days after its cutoff
- Claude Opus 5.597 days after its cutoff
- Gemini 4 Hydrogen188 days after its cutoff
- Grok 4.7127 days after its cutoff
None of these four assistants can know about it. The closest, Claude Opus 5.5, stops 97 days before it.
Key facts
- Architecture: each Muse instance runs in a kernel-based virtual machine (KVM) connected to, but meant to be isolated from, Meta’s infrastructure
- Internal post by VP of Core Infrastructure Surupa Biswas, VP of Engineering Francois Richard and Senior Director Josh Barry: ‘A sudden spike in reported KVM escapes, plus heightened awareness of agentic safety issues made us rally on a service hardening push’
- Timeline per 404 Media: hardening push began Aug 27; Muse launched in early September; an internal post on Sept 18 discussed the push
- Meta’s bug bounty lists a breach of the Muse-to-production boundary as its highest-impact category, paying up to $300,000
- Mac security researcher Patrick Wardle called the design ‘inherently risky’, saying production access is ‘one KVM escape away’
- Meta statement: ‘Muse is the first personal AI agent built for everyone and we’re proud of the work we’ve done to make it safe, secure and private, with built-in protections and user controls that put people in charge.’
- No exploited breach was reported; the concern is about how thin the isolation layer is for an agent that holds users’ email, bank and account access
What happened
404 Media saw internal Meta posts about a security push before Muse’s launch. Meta found and fixed several ways for code running inside a Muse sandbox to reach the host or other users. Some engineers doubt the fixes are enough. The paywalled parts of the story are summarised here from 404 Media’s public text and from Futurism and Slashdot; quotes should be checked against the original.
Why it matters
Muse holds credentials for users’ email, bank and shopping accounts and runs code for them. If one VM escape works, it could expose many users at once. The report adds to a week of criticism of Muse’s privacy design (relationship profiles, leaked instructions).
Sources
4 sources from 4 sites. Numbers match the chips in the text.
4 sources: 3 press, 1 reaction
Press
- 404 Media: Meta rushed to fix Muse ‘VM escape’ vulnerability soon before launch404media.co, press
- Futurism: Meta insiders convinced Muse is going to end up leaking the bank accounts and email archivesfuturism.com, press
- Yahoo Tech: Meta rushed to fix a Muse VM escape vulnerability before launchtech.yahoo.com, press
Reactions
- Slashdot discussionyro.slashdot.org, discussion
Changes
- Filed (via Futurism’s follow-up)