Meta pauses Muse chat sharing after links found in DNS records
Claroc says 6,800 Muse share links could be found through public DNS records, some holding business details. Meta paused sharing while it reviews the report.
Meta paused the sharing feature in Muse, its personal AI agent, on 20 October 2026 after security firm Claroc reported that shared conversations could be found through public DNS records. Claroc says one search of a commercial passive-DNS service returned more than 6,800 share hostnames. It opened a few hundred of them, without logging in.
Most pages Claroc opened were harmless. A minority held sensitive material, including a small-business loan application, an internal revenue review, a bank fraud alert with a partial account number, and a staff vacation calendar. Claroc says it found no evidence of misuse, but it cannot tell how long the pages were reachable or whether others found them first.
Why it matters
A shared Muse chat was a public page that anyone with the link could open. Each address included the conversation's title and a random ID. Because that title sat in the hostname, it was recorded in DNS history, where it could be searched. Search engines were not involved, so nobody needed to be sent the link.
This is a useful lesson beyond Muse. A share link can feel private, but it may publish the page, and the address itself can reveal the topic.
Meta said it had "paused this functionality while we review this report", according to PPC Land. Claroc says that when it rechecked 40 shares on 20 October, none opened, though their hostnames and titles remain in DNS history. PPC Land reports that Meta has not said how many shares existed or whether users will be told. Claroc says it reported the issue on 8 October, which Meta has not confirmed.
The 6,800 figure counts hostnames seen by one provider, not people affected. Claroc also sells security monitoring for AI tools, so its advice partly fits its business.
What you can do
- Treat anything shared through an AI assistant as public, and read it before you share.
- Keep financial, staff and client details out of shared chats.
- If you shared a Muse chat, assume its title may remain in DNS records, and tell anyone affected if it was sensitive.
- If you run a team, tell staff that share links publish content, and find out whether anyone uses Muse for work.
- Check the sharing settings of other AI tools your team uses.
Sources
Source: Claroc