Meta paused Muse's sharing feature on October 20 after researchers found that strangers could discover links to shared conversations. If you've used Muse to share work, review what you sent. Some pages contained sensitive business documents, and a hard-to-guess link offered less protection than it appeared to.
Claroc's research team found more than 6,800 share addresses and inspected a few hundred. Most of the pages it opened were ordinary material. Others included a loan application and an internal revenue review. That count describes discovered addresses, not 6,800 confirmed leaks of confidential documents.
How the links became findable
Muse put the conversation title and a random identifier into each share's hostname, the domain name a browser looks up before loading a page. Historical DNS services recorded those names. Claroc could find the addresses there without having anyone send it a link. As the researchers put it: "It took one query."
Blocking Google from indexing a page wouldn't fix that design. The information was travelling through the address lookup itself. A title can reveal something sensitive even when the underlying document is no longer available. Think about what you'd learn from the name of a confidential meeting, before reading any notes.
Dan Goodin at Ars Technica obtained Meta's response: "we've paused this functionality while we review this report". Claroc then rechecked 40 previously accessible shares; none opened. It says the hostnames, including titles, remain in DNS history. The researchers couldn't establish whether anyone else had accessed the pages earlier.
Review the material you shared
Start with the documents behind your links. Were they intended for anyone who found the address, or only for the colleague you sent it to? For confidential work, tell whoever owns the material what was shared and when. They can judge the consequences with the actual document in front of them.
Don't assume every incident calls for the same response. A draft marketing paragraph and an active password need different treatment. If you shared a live credential, replace it. If you shared a forecast or personnel information, removing the page won't make a copy disappear from someone's inbox. Keep your own record of the affected material without creating another public link to it.
This is also a good moment to check other AI sharing tools you use. Open a harmless test link in a signed-out browser. Ask whether the recipient must authenticate and whether you can revoke access. A link that works for anyone who has it deserves a clear warning before you publish.
A better model can't repair a sharing feature
Our Muse Wonder coverage looked at Meta's push for stronger memory and longer-running tasks. That makes the surrounding product more consequential: the assistant accumulates useful context, and its sharing controls decide where that context goes.
Use named-recipient access before sharing sensitive work through an agent. For now, use a document service whose access controls you understand, and give colleagues permission there. Meta has stopped these pages from opening in Claroc's sample. The next version of Share should make the audience obvious before anyone clicks it.
Cover: AI-generated editorial illustration by TMRW using Meta branding. The document contains no real user information.
