Meta Pauses Muse Link Sharing After DNS Exposure Found Thousands of Chats
Meta has paused link-based sharing for Muse conversations while it reviews a report that shared chats could be found through public DNS records. The pause was confirmed October 20, 2026, after security firm Claroc said it found more than 6,800 Muse share links. The Verge
Ars Technica published a report titled "Meta Muse exposes users' personal and business secrets when they share conversations" on October 20, 2026. Ars Technica
Claroc said it found the links by searching public DNS records, the shared logs that map website names to computers. The method did not require guessing web addresses or breaking into accounts. It used hostnames that had already been recorded in DNS data.
Each Muse share builds its web address from the share's title and a random ID. That structure means a full link can be rebuilt from a hostname taken from DNS. Muse spokesperson Tracy Clayton said the sharing feature creates a page accessible to those with the link and that Meta paused the feature while reviewing the report and considering changes to link discovery. The Verge
By rebuilding URLs this way, Claroc said it was able to view hundreds of Muse conversations. The examples included a marketing company's revenue review, a small business owner's loan application, a workplace's full-year staff calendar, and notes for a job candidate's call with an AI lab.
The risk comes from what Muse can do. Meta's Muse is a personal AI agent that books trips, makes purchases and places calls for users. Meta launched the Muse AI agent with the ability to access other apps to send emails and make payments. Reuters Meta launched Muse in the U.S. via a dedicated app and WhatsApp. The launch took place September 8, 2026. Muse topped U.S. app download charts after its launch.
Shared Muse threads are not short prompts. They can carry itineraries, payment context, calendars, business documents and job-search preparation in a single transcript.
The broader context here is that unlisted web addresses keep failing as a privacy boundary when the address itself leaks through infrastructure. A share link works like a key. Anyone who holds it gets access. Passive DNS collection, resolver logs and crawling turn hostnames into searchable inventory, especially when the hostname includes a readable title. Random IDs help against guessing. They do not help once the complete hostname has been logged elsewhere.
In my view, the fix is well understood, and that is reason for measured optimism. Expiring links, asking viewers to log in, removing titles from hostnames and turning off indexing by default would keep sharing convenient while removing DNS as a way to find chats. For agents that touch email, payments, travel and calendars, those controls should be standard rather than optional. The pause gives Meta room to make that shift before sharing spreads further as Muse adoption grows.
