Meta suspends Muse sharing after 6,800 chat links exposed
Security firm Claroc found more than 6,800 shared Muse conversation links listed by readable title in public DNS records, prompting Meta to suspend the feature on 20 October 2026.
Photo: EngadgetKey points
Meta suspended its Muse chat-sharing feature after security firm Claroc found more than 6,800 shared conversation links discoverable through public DNS records.
Meta suspended the conversation link-sharing feature in its Muse AI agent on 20 October 2026, after security firm Claroc found more than 6,800 shared conversation links listed by readable title in public DNS records. Claroc published its GhostShares research on 18 October 2026, ten days after reporting the issue to Meta's bug bounty programme on 8 October 2026. When Claroc rechecked 40 shares on 20 October 2026, none opened.
The exposure matters because Muse is Meta's general-purpose AI agent, launched on 8 September 2026, capable of searching the web, filling out forms, booking appointments and connecting to user accounts. Unlike a note-taking app, it reaches calendars, professional correspondence and connected services. The flaw did not affect private sessions, which Meta's documentation describes as isolated cloud environments, but it did affect conversations users deliberately shared through the feature, whose links anyone could find.
How the links became findable
Muse builds each share's web address from the conversation's own title plus a random ID, served from hostnames under cf.metaaiusercontent.com, the content domain Muse serves shares from. When someone opens a share, the browser resolves that hostname, and passive-DNS providers whose resolvers observe the lookup record it and keep it searchable. The title a user typed therefore lands in a public index of domain names, producing addresses like q3-revenue-review-7b1e42f0.cf.metaaiusercontent.com.
Claroc searched one commercial passive-DNS service for Muse's content domain and, after filtering out wildcard-DNS scan noise, found more than 6,800 share hostnames listed by title. The firm opened only a few hundred and said almost every live share opened on sight, without an account. Passive DNS was not the only channel: urlscan.io, a public URL-scanning service, already held more than 75 saved scans of Muse share pages. Claroc called these findable pages GhostShares.
Claroc described six sensitive shares by category only, withholding names and links: a candidate's notes preparing for a confidential executive-search call with a frontier AI lab, naming the lab's internal contact and meeting time; a national marketing company's internal revenue review marked for its CEO; a small-business owner's loan application with the amount requested; a to-do list containing a bank fraud alert with a partial account number and a transaction amount and time; a real-estate investor's internal performance report with two property addresses and exact return, income and mortgage figures; and a workplace's full-year staff vacation calendar listing dozens of employees against the weeks each would be away.
What the opened pages held
Claroc said it reached every page without being given its link, working from a domain-lookup dataset with no account, and that it did not log in, fill in a form, or upload anything; one page asked for a password and the firm left it. Every severity judgment came from a person reading the page. Claroc stated it has no evidence anyone misused the shares, that it did not contact the people or companies involved, and that the two companies whose documents it found are real, confirmed against public sources.
Muse's robots.txt asks search and AI crawlers to stay off the share paths, but Claroc noted that robots.txt governs crawling rather than access, and its discovery never went near a search engine. Each address carries a random ID long enough that nobody could guess it, yet the first time anyone opens a share, DNS logs the full hostname, ID included. Claroc said this class of leak has precedent: in 2025, shared ChatGPT conversations surfaced in Google results and OpenAI removed the option that made them indexable, and Google later indexed more than 370,000 Grok conversations.
Claroc reported the issue to Meta's bug bounty programme on 8 October 2026, with reproduction steps and example shares. Its content checks were made during collection on 7 and 8 October 2026, and on 18 October 2026 it re-opened the call-prep share once to capture a redacted screenshot. Passive DNS showed the share tier still minting new hostnames, 27 on the day Claroc last looked, which the firm described as continued discovery rather than re-verified access.
Disclosure timeline and recheck
Meta's Help Center documentation for sharing a link to an AI conversation states that "people with the link will be able to see your conversation," that the link does not expire, and that people can share the link onward. The conversation is captured at the point the link is created, and deleting the link cuts off access for people who received it. Claroc noted the page documents Meta AI rather than Muse specifically, but described it as the closest published description Meta gives of how one of its AI share links behaves.
Meta's separate Muse privacy and security documentation states that every Muse user's cloud virtual machine is isolated so no one else's agent can access it. In a statement to Ars Technica, Meta said "we've paused this functionality while we review this report and consider changes to how these links can be discovered."
What Meta's documentation says
Claroc characterized its findings as one discovery channel, one hostname pattern and one product over a short window, rather than a measure of Muse's total exposure. The hostnames themselves, conversation titles included, remain in passive-DNS history even though the pages no longer open. Meta has not published a date for restoring the sharing feature, and the review of how links can be discovered remains underway.
Frequently asked questions
How many Muse shared links did Claroc find?
Claroc found more than 6,800 Muse share hostnames listed by readable conversation title in public passive-DNS records, and opened a few hundred of them, almost all of which opened without an account.
How did the Muse share links become publicly discoverable?
Muse built each share's address from the conversation title plus a random ID under cf.metaaiusercontent.com. When a share was opened, DNS logged the full hostname, and passive-DNS providers kept it searchable by title.
When did Claroc report the issue and when did Meta act?
Claroc reported the issue to Meta's bug bounty programme on 8 October 2026 and published its research on 18 October 2026. Meta suspended the sharing feature on 20 October 2026.


