Meta reissues Muse shared artifact URLs after researchers exposed discoverable links

What happened

Meta has switched sharing back on in Muse, its chat product where conversations can include artifacts such as documents and images, and it has issued replacement web addresses for every artifact shared before the fix. The change follows a report from security researchers who demonstrated that links people reasonably believed were private could be found by outsiders with little effort.

According to The Verge, Meta's David Singleton announced the change in a post on X, saying the underlying problem has been resolved and that sharing is available again.

How the links were exposed

Researchers at Claroc reported earlier this week that Muse built the web addresses for shared conversations out of each conversation's title, and that those addresses were written into public DNS. Because DNS records can be queried by anyone, the hostnames could be surfaced without ever receiving the original link from its owner.

The researchers said they had located real shared pages this way, including a marketing company's internal revenue review and a small business owner's loan application. The Verge also notes that Ars Technica reported Meta had paused the sharing feature entirely after being contacted about the findings.

What Meta changed

Singleton, according to The Verge, framed the flaw as specific to the URLs of shared Muse artifacts rather than a defect in how chat sharing works. That is a somewhat narrower characterization than the researchers' account, which centered on shared conversation links, but both descriptions point at the same class of problem: predictable, publicly visible addresses doing the job of real access control.

The remedy is a blanket reissue. Any artifact shared before the fix now lives at a different URL, and anyone who opens an old link sees a message telling them to obtain the updated address from the person who shared it. Singleton acknowledged that this is inconvenient and apologized for the disruption, saying that protecting user data had to take priority.

Why it matters

The episode is a reminder that "anyone with the link" is not a privacy model. When a service derives URLs from human-readable titles and lets those hostnames enter public DNS, the links stop being obscure and become discoverable by anyone motivated to look.

Shared AI conversations are especially sensitive in this respect. As the Claroc findings show, they can hold business financials and personal loan paperwork rather than casual chatter, so a weak link scheme converts a convenience feature into a data exposure.

For Muse users, the practical takeaway is straightforward: artifact links created before the fix are dead, and anything you still want people to see needs to be re-shared with its new address. For everyone else, the reasonable assumption is that a shared link without explicit access controls may eventually be found — and that sensitivity should be judged accordingly before hitting share.