Meta Re-enables Muse Sharing After Fixing Public Link Flaw

Meta re-enabled Muse sharing after researchers found public links exposed documents such as internal revenue reviews and loan applications. Previously shared artifact links now have new URLs, forcing teams to update workflows.

What happened

Meta has re-enabled Muse sharing after security researchers reported that public conversation links could be easy to find. The researchers said they had been able to find Muse pages such as a marketing company’s internal revenue review and a small business owner’s loan application.

Researchers at Claroc reported earlier this week that Muse web addresses for shared conversations were named after a conversation’s title and written into public DNS. Ars Technica said Tuesday that Meta paused the sharing feature after it reached out about what was going on.

In an X post, Meta’s David Singleton said the underlying issue is now fixed and sharing is back on. According to Singleton, the issue was with URLs for shared Muse artifacts, which Meta says are things like documents and images inside Muse, and was not a flaw with chat sharing.

“If you shared an artifact before the fix: it now has a new URL,” Singleton says. “Anyone visiting the old link will see a note asking them to get the new one from you. We know that’s a pain, and we’re sorry for the disruption — but protecting user data has to come first.”

Key facts

• Meta re-enabled Muse sharing after temporarily pausing the feature.
• Security researchers found public Muse pages that included a marketing company’s internal revenue review and a small business owner’s loan application.
• Claroc reported that Muse web addresses for shared conversations were named after a conversation’s title and written into public DNS.
• Meta said the flaw affected URLs for shared Muse artifacts, including documents and images inside Muse, but not chat sharing.
• Shared artifacts from before the fix now have new URLs; old links show a note asking visitors to get the new link from the sharer.

Our analysis

For social media managers, creator teams and brand operators, this incident is a reminder that AI collaboration tools can become an accidental distribution channel for sensitive material. The reported examples of an internal revenue review and a loan application suggest that users were treating Muse as a workspace for business documents, not just casual chat. A public DNS naming pattern tied to conversation titles likely made links easier to discover or stumble across, which increases the risk of search engines or third parties indexing confidential artifacts.

The fix changes publishing behavior in a deliberate way: previously shared artifact links now break by design. That is a trade-off between continuity and privacy. Operators who embedded Muse links in content plans, client reports, campaign briefs or internal wikis will likely find those links no longer work. The apology from Meta for the disruption suggests the company expects this to be inconvenient for active users.

This also marks a shift in how Meta is handling AI artifact sharing. Pausing the feature after Ars Technica reached out, then re-enabling it with a new URL system, shows that security fixes for AI sharing features can be fast but disruptive. It should push teams to treat AI-generated artifact URLs as perishable access points rather than permanent storage.

What it means for operators

• Audit any Muse artifact links you have shared with clients, collaborators or internal teams; ask the original sharer for the new URL and update your docs.
• Avoid putting sensitive or client-confidential content in Muse conversation or artifact titles, because the reported flaw tied public addresses to those titles.
• Before sharing AI-generated documents or images externally, open the generated link in a logged-out or private browser to see what a visitor can actually access.
• Treat AI artifact URLs as short-lived links: do not use them as permanent storage in content calendars, campaign briefs or onboarding docs; keep source files elsewhere.
• If your team uses Muse for internal reviews, establish a rule that revenue, legal, HR or loan-related material stays out of shared AI artifacts until you have a separate access control review.