Security firm NebuSec published research on 20 November showing how a single attacker-controlled webpage could break out of the layered sandbox around Meta Muse, Meta’s cloud-hosted AI assistant. The end result was root inside the user’s virtual machine, access to Muse’s secure credential storage, and the ability to read and rewrite the user’s chats and stored memories. NebuSec says Meta’s Muse team “was aware of every finding” and “had patched all exploits” by the time of publication.
How Muse is supposed to be locked down
Per NebuSec’s technical writeup, each Muse user’s agent runs in a dedicated VM, with a runtime container inside it separating the agent from more privileged resources. A service called Sentinel watches outbound traffic and asks the user to approve network requests, and a separate credential service keeps real connector credentials out of the agent’s environment.
The chain, step by step
- Stale browser. Muse uses a bundled Chromium to render pages, for example when exporting a web page to PDF. NebuSec says its snapshots showed that browser lagging Chrome releases: in early October the container still had Chromium 152.0.7977.82, a patch release from 3 September. That left public V8 bugs usable, including one NebuSec had reported. Asking the agent to export an attacker’s page gave code execution inside the runtime container.
- Sentinel gap. Weaknesses in how Sentinel classified outbound requests let NebuSec send conversation history and stored memories to an outside server without triggering an approval prompt, and also modify them.
- Kernel escape. Using its automated exploit generator, NebuSec built Linux kernel exploits against the shared kernel (Linux 7.0, within the ranges of several published CVEs). They escaped the container and got root in the user’s VM, which exposed persistent storage, secure credential storage and Sentinel itself, and allowed network traffic outside Sentinel’s container-level control. NebuSec says the exploits worked in more than 99.9% of its test runs.
NebuSec stresses the limits: the compromise stayed inside one user’s VM. It did not show an escape to the hypervisor host or into other users’ environments.
What we have and have not seen
The patch status comes from NebuSec, not from Meta, and NebuSec gives no CVE IDs for the Muse-specific issues or a disclosure timeline beyond saying it reported them. This is separate from the earlier Muse problem we covered, where shared chat links leaked through passive DNS, and from Muse’s undeclared agent fingerprint. Another case of an agent toolchain being turned against its target is Amazon’s report of attacker AI agents finding a MONAI Label zero-day.
Why this matters
Muse had sandboxing, privilege separation, credential isolation and an egress monitor, and NebuSec still went from one rendered webpage to the credential store, because each layer leaned on the one below it. For anyone building agents, the takeaways are concrete. Patch bundled browsers on Chrome’s schedule, enforce egress outside the box you are trying to contain, and assume a container escape when you decide what the VM may hold.

The Campfire
CommentsThanks. Your comment is waiting for the desk. Once it is approved it appears here within about a minute.
Add a comment