Threat assessment: contained, for now. Meta has turned sharing back on in Muse after security researchers showed that links to shared content could be found by outsiders. The Verge AI reports that Meta paused the feature earlier this week. Meta’s David Singleton now says the problem is fixed. For anyone who shared Muse content before the fix, though, there’s still work to do.
🎯 What Happened
The sequence was quick:
- The report. Researchers at Claroc found that web addresses for shared Muse content were built from the conversation’s title and written into public DNS.
- The exposure. The researchers said they found pages including a marketing company’s internal revenue review and a small business owner’s loan application.
- The pause. Ars Technica reported Tuesday that Meta paused sharing after the outlet contacted the company about the issue.
- The fix. Singleton posted on X today: “The underlying issue is now fixed, and sharing is back on.”
According to The Verge AI, Singleton said the flaw affected URLs for shared Muse “artifacts.” Meta describes these as items like documents and images inside Muse. He said chat sharing itself wasn’t the problem.
🔍 Why DNS Made This Worse
This wasn’t a typical “anyone with the link” mistake. Shared links usually rely on being hard to guess. If nobody hands you the URL, you won’t find it.
DNS is the internet’s public address book. It turns names into server locations. Third parties often log and index those records, and they can be searched. Once a descriptive title became part of an address published in DNS, the link wasn’t secret anymore.
That makes it a double failure:
- Readable names. A title like a loan application tells a searcher exactly what’s behind the link.
- Public publishing. Putting those names in DNS let people find them without ever receiving a link.
A long random string kept out of public records would have avoided both problems. That’s standard practice for private-by-link sharing, so this kind of slip is hard to excuse.
⚠️ What Changes for Users
Meta’s fix comes with a cost. Every artifact shared before the fix now has a new URL.
“Anyone visiting the old link will see a note asking them to get the new one from you,” Singleton said. He added: “We know that’s a pain, and we’re sorry for the disruption,” and said “protecting user data has to come first.”
That’s the right call. Old links had already leaked through DNS, so the only real fix was to retire them. It does mean anyone who passed Muse documents to clients, lenders or colleagues will need to send them again.
📋 Tactical Points
If you or your team use Muse:
- Reshare anything important. Old artifact links won’t show the content anymore. Send the new URLs directly.
- Treat earlier shares as possibly exposed. If you shared sensitive files before the fix, assume someone outside your list may have seen them. Act on that.
- Remember that chat sharing wasn’t affected, according to Meta. The problem was limited to artifacts.
- Check your company’s AI policy. If staff put revenue reviews and loan applications into a consumer AI tool, that’s a governance gap worth closing.
🧭 The Bigger Pattern
We’ve seen this before. AI assistants keep adding sharing features, and public links keep leaking private work. People treat these tools like private workspaces. Then a sharing setting or URL design turns that work into something searchable.
What stands out here is the kind of content involved. AI tools increasingly produce finished work like documents, reports and images, not just chat replies. That raises the stakes. A leaked chat is embarrassing. A leaked revenue review or loan application can hurt a business.
Meta moved fast once it was alerted, and the fix looks sound. Still, a researcher found this before Meta did. Expect more scrutiny of how AI companies build share links, and expect business users to start asking where their files actually end up.
More details are available in the original report from The Verge AI.