AivexaNewsSearch
AI news for builders and product teamsChecked every hour

Meta Muse exposes users' personal and business secrets when they share conversations

Collected Oct 20, 2026

Meta has paused the link-sharing feature in Muse, its general-purpose AI agent, after researchers at security firm Claroc showed that shared conversations could be discovered by anyone and often contained sensitive material. The researchers reported their findings Monday, and Meta confirmed the suspension to Ars Technica in response to questions about the behavior, saying it is reviewing the report and considering changes to how these links can be discovered.

The mechanics are the interesting part. When a Muse user shares a search, conversation, image or similar artifact, the service creates a page reachable through a unique URL. Muse builds those URLs on the domain cf.metaaiusercontent.com and places the conversation's title in the subdomain rather than in the path, followed by a long random-looking string. Simplified examples of the pattern the researchers described look like q3-revenue-review-7b1e42f0.cf.metaaiusercontent.com or loan-application-draft-a4c9e2.cf.metaaiusercontent.com. Because that title sits in the hostname, it lands in public DNS records the moment someone resolves the link.

That is what made enumeration cheap. Passive DNS services archive historical mappings of domain names to IP addresses and related records, collected from sensors at recursive resolvers and similar infrastructure. Once a recipient clicks a shared link, the lookup is recorded in searchable commercial databases. Claroc said a single query against such a service surfaced 6,800 Muse share links that users had created. The researchers opened a few hundred of them and found material that was plainly not meant for public view.

Among the examples they cited: a job candidate's notes preparing for a confidential executive-search call with a frontier AI lab, including the lab's internal contact and the meeting time; a national marketing company's internal revenue review addressed to its CEO; a small-business owner's loan application with the requested amount; a to-do list containing a bank fraud alert with a partial account number and a transaction amount and time; a real-estate investor's performance report with two property addresses and exact return, income and mortgage figures; and a workplace's full-year vacation calendar listing dozens of employees by week. Claroc's take was that amassing such a set would normally be expected to take real effort, and here it took one query. The firm calls the exposed pages GhostShares: content that opens for people who were never handed the link and can locate it on their own.

Timeline matters here. Claroc co-founder and CTO Asaf Aprozper said he submitted the findings through Meta's Muse bug bounty program on October 8 and also tried to reach Meta staff on LinkedIn, without a reply either way. Meta's statement to Ars framed the bounty program as the channel for researchers to raise scenarios and said the company had paused the sharing functionality while it reviews the report. The suspension closes this particular exposure for now, but it does not retroactively unshare pages that were already indexed or cached elsewhere.

Context worth keeping in mind: last month CEO Mark Zuckerberg described Muse as built from the ground up for privacy and security. The agent has climbed to the top of Apple's App Store rankings and works by autonomously filling out forms, booking appointments, making purchases, creating documents and taking other actions on a user's behalf. To do that it needs access to most of a user's accounts, which raises the stakes on any leak of conversation content, since the conversations themselves can contain account details, schedules and financial figures. Three weeks after launch, macOS security researcher Patrick Wardle found a zero-day that let any other app on the same device take full control of a Muse account; Meta played down the severity on the grounds that exploitation required an already-compromised device, and did not acknowledge Wardle's finding that a ClickFix attack was sufficient to hijack an account.

My reading is that the URL design is the crux. Putting human-readable titles in a subdomain is a common pattern for making links legible, and it is not inherently wrong, but it interacts badly with two facts of the web: DNS lookups are observable by third parties, and users tend to type descriptive titles into share dialogs. The random suffix adds entropy against guessing, yet it does nothing against enumeration through passive DNS, because the title portion is what makes records easy to filter for. Had the title lived in the URL path instead of the hostname, the share pages would not appear in public DNS at all; discovery would then require guessing full hostnames.

The broader lesson for anyone shipping share links is that secrecy by unguessable URL only holds if the URL never becomes observable. Hostnames leak through DNS, referrer headers, email scanners and link previews; path segments leak less often. Product teams building AI assistants with broad account access should treat share links as public artifacts and consider expiry, revocation and an explicit warning about what the transcript contains. For Muse users, existing links may still resolve or remain in third-party caches even after Meta's pause, so the cautious move, in my inference, is to assume anything shared before the suspension should be treated as potentially public.

Why it matters: Meta's suspension limits further discovery of new Muse share links, but developers and product teams should read this as a design lesson about putting user-chosen text into hostnames. Anyone building a share feature for an AI assistant, especially one with account-level access, now has a concrete case showing that unguessable URLs are not private when their structure is indexed. Expect tighter scrutiny of Meta's privacy claims for Muse, and likely pressure on other assistant vendors to audit how their own share links are constructed and discovered.

Read at Ars Technica · AI

Based on reporting from the original publisher. Visit the source for full context and later updates.

Publisher excerpt

Meta is suspending the sharing feature while it investigates its privacy.