Muse Chat Sharing Paused: What the GhostShares Issue Means for You
Share
On October 20, 2026, Meta told Ars Technica it had paused Muse's chat-sharing feature while it reviews a report about how shared conversation links could be found. The issue affects only chats people chose to share — but it is a useful reminder that a share link is public by design.
This article explains what happened in plain language: how the sharing feature worked, how a security firm found the exposed links, who is affected, and what to do if you shared a Muse conversation.
Quick answer: Meta has paused Muse chat sharing after security firm Claroc showed that shared conversation links could be found in public internet records, because the links were built from chat titles. Only chats people chose to share were affected. If you shared a Muse chat, assume its title is public and delete the link if you still can.
What happened
Muse is Meta's personal AI agent, launched in the United States on September 8, 2026, then in Canada on September 18 and in Japan on October 23. It lets you share a conversation by creating a link, so anyone with the link can read it.
On October 8, 2026, security firm Claroc reported the problem to Meta through its bug bounty program. According to Claroc, the share links were built in a way that made them findable by strangers — not just by the people you sent the link to. Meta told Ars Technica on October 20, 2026 that it had "paused this functionality while we review this report and consider changes to how these links can be discovered."
That is the whole story so far: a researcher found a weakness in how share links were made, reported it privately, and Meta paused the feature. There is no report of a data breach at Meta, and Claroc says it has no evidence anyone misused the shared conversations it found.
How the shared links could be found
The problem was in how Muse built the share link. When you chose to share a conversation, Muse created a web address from the conversation's title, plus a random ID. The title went into the subdomain — the part of the address before the main domain name.
That matters because domain names are logged in public passive-DNS records. Because the chat title sat inside the domain name itself, anyone who could query those records could see the titles of shared conversations, and from there work out the full share link.
Claroc says it found about 6,800 share links that could be listed this way with a single passive-DNS query, and it opened hundreds of them to check what was inside. Most were unremarkable — everyday chats with nothing sensitive in them. A minority was sensitive. The examples reported include a small-business loan application, a staff vacation calendar, and a bank fraud alert that contained part of an account number.
To be clear about what this was not: nobody had to guess your password or break into your account. The links were working as designed — open to anyone who had them. The weakness was that they were easier to discover than users probably expected.
Who is affected — and who is not
Only chats that people chose to share were affected. If you never shared a Muse conversation as a link, this issue does not touch you: your private chats were not part of the exposed links.
If you did share a Muse chat, what happened to that link? When Claroc rechecked 40 shared links on October 20, none of them opened anymore — the pause appears to have stopped the links from working. But the titles remain in passive-DNS history, so a record of your shared conversation title may still be visible there even though the link no longer opens.
Two important things Meta has not said. First, Meta has not said whether the old share links were deleted, or only stopped from opening for now. Second, Meta has not said whether it will notify the people who shared conversations. Until Meta says more, the honest answer is: we do not know. Check Meta's official pages for updates rather than relying on rumours.
It is also worth keeping the scale in proportion. About 6,800 links were enumerable from one query — but Muse is used by millions of people, and most shared chats the researchers opened contained nothing sensitive. The risk is real for the small number of people who shared something private, and small for everyone else.
What to do now if you shared a Muse chat
Claroc's advice is straightforward: assume anything you share is public until you have checked. Here is what that means in practice.
First, assume the title of any chat you shared is public. Titles often give away more than people realise — a loan application, a holiday plan, a health question. If the title alone would bother you if a stranger saw it, treat it as seen.
Second, delete the link or the conversation if you still can. Open Muse, find the shared conversation, and look for the option to remove the share link or delete the chat. If the sharing controls are gone while the feature is paused, delete the conversation itself.
Third, check what was in the shared chat. If it contained account numbers, addresses, or passwords, act as you would for any exposure: change the affected passwords, watch the account for unusual activity, and contact your bank if financial details were involved. The bank fraud alert in Claroc's examples contained only part of an account number, but partial details are still worth taking seriously.
Fourth, change how you share in future — with any AI assistant, not just Muse. Before you share a conversation, read the title as if a stranger will see it, and rename it to something neutral first. Share only the specific chat you mean to share, and remove the link when the other person has read it.
Finally, if you are new to Muse, Muse registration assistance helps you create your own Muse account for personal use, per Meta's platform terms — so your chats and your account stay yours from day one.
Frequently asked questions
Is every Muse chat affected by the GhostShares issue?
No. Only conversations that people chose to share as a link were affected. If you never shared a Muse chat, your conversations were not part of the exposed links. The issue was about how share links could be discovered, not about private, unshared chats.
Can someone still open my shared Muse chat link?
Probably not right now. When Claroc rechecked 40 shared links on October 20, 2026, none of them opened anymore, which suggests the pause stopped the links from working. But the titles remain in passive-DNS history, and Meta has not said whether the old links were deleted. If you can still delete the link or the conversation, do so.
Did anyone misuse the shared Muse chats?
Claroc says it has no evidence anyone misused the shares it found. The firm opened hundreds of links to verify the issue and reported it to Meta privately. That does not prove no one else ever found a link, but no misuse has been reported.
Is Muse still safe to use?
Muse itself has not been reported as breached, and the issue was limited to the sharing feature, which Meta has now paused. Muse runs in an isolated secure virtual machine, and Meta says it does not see real passwords or card details and asks before sensitive actions. As with any AI assistant, the sensible rule is the same: do not share conversations that contain private details. If you are getting started, this Muse registration assistance can help you set up your own account.