I asked Meta’s Muse for its filesystem and it sent me 6.8GB
Points and comments are a snapshot, not live.
A user tricked Meta's Muse AI into exporting its entire Linux filesystem, including SSH keys.
The author asked Muse to archive visible files and send them to Google Drive. The 6.8 GB export contained the root filesystem, internal documentation, integration code, app templates, memory records, container setup scripts, and SSH key files. The system uses a sandboxed Linux environment per user. Internal docs revealed unreleased connectors (Slack, Dropbox, Polymarket, Canva) and an experimental ESP32-based Home Link bridge. Codex CLI was installed but only its sandboxing tool was used. The author reported this to Meta's bug bounty program, which marked it "Not Applicable."
What commenters are saying
Most commenters argued this is not a vulnerability because each user gets their own VM sandbox, and everything inside it is expected to be accessible to that user. Multiple commenters noted the file system is visible through the app's UI file explorer anyway. Some pointed out that while SSH keys were found, they are likely per-user keys generated for the VM. A minority argued that exposing internal documentation and unreleased features constitutes a security concern. The author's report was marked "Not Applicable" by Meta's bounty program, which several commenters defended as correct policy.