Skip to the content
AI and Cybersecurity Learning and Practice Center Test automation Open the Learning Center

NewsIncident

Meta turns Muse sharing back on with new links after 6,800 shared pages turned up in passive DNS, titles and all

Claroc published on October 18 that Muse, Meta's assistant launched on September 8, put each shared artifact on its own hostname under cf.metaaiusercontent.com, built from the conversation's title plus a random ID, so one query to a commercial passive DNS service returned more than 6,800 share hostnames that opened without a login. Claroc opened a few hundred and describes a candidate's preparation for an executive search call with a frontier AI lab, a marketing company's internal revenue review, a small business loan application, a to-do list with a bank fraud alert and a partial account number, a real estate investor's report and a workplace vacation calendar covering dozens of employees. It reported the issue to Meta's bug bounty program on October 8 and says it got no response; after Ars Technica reported the findings on October 20, Meta paused sharing while it reviewed the report. On October 22 Meta's David Singleton wrote that the underlying issue was fixed and sharing was back on, with new addresses for artifacts shared before the fix and a note on the old links asking for the new one; he said the flaw affected shared Muse artifacts, not chat sharing, and that the Muse bug bounty pays up to 300,000 dollars. Claroc found no evidence of misuse, and notes the old hostnames stay in passive DNS history.

Why it matters

Anyone-with-the-link sharing is only private while nobody can list the links, and a hostname is a list anyone can read. Before your team shares an AI conversation, ask where the link will live and who keeps the DNS.

Sources

Read it with the rest of the news in the Learning Center