Meta Muse Security Flaw Exposed 6,800 Private Conversations Through DNS Leak

Reviewed byNidhi Govil

13 Sources

Share

Meta suspended its Muse AI assistant's sharing feature after security researchers discovered a design flaw in share links that exposed sensitive user data. Claroc researchers found over 6,800 shared conversations containing confidential documents, loan applications, and business secrets through a single passive DNS search.

News article

Meta Suspends Muse Sharing After Major Data Exposure

Meta Muse, the company's newly launched AI assistant, faced a critical security flaw that exposed thousands of private user conversations. Security researchers at Claroc discovered they could access 6,800 shared conversations through a single passive DNS search, revealing sensitive information that users clearly never intended to share publicly

1

2

. Meta responded by suspending the sharing feature while reviewing the issue and considering changes to prevent such privacy vulnerabilities

2

.

The exposed data included a small-business owner's loan application with requested amounts, a national marketing company's internal revenue review marked for its CEO, confidential executive-search call notes naming a frontier AI lab's internal contact and meeting time, a real-estate investor's performance report with property addresses and exact mortgage figures, and a workplace's full-year staff vacation calendar listing dozens of employees

1

3

. Researchers also found a to-do list containing a bank fraud alert with partial account numbers and transaction details

2

.

How the Design Flaw in Share Links Enabled Discovery

The privacy vulnerability stemmed from a fundamental design flaw in how Meta Muse constructed shareable URLs. Like many online services, the Muse AI assistant allowed users to create unique links for sharing conversations, typically protected by long random strings that prevent easy guessing

1

. However, Meta Muse placed conversation titles directly in the URL subdomain alongside random identifiers, making them visible in passive DNS searches

2

.

All shared conversations used the domain cf.metaaiusercontent.com with URLs structured like home-sale-budget-9f21c8a3.cf.metaaiusercontent.com or q3-revenue-review-7b1e42f0.cf.metaaiusercontent.com

1

. When someone clicked a share link, passive DNS systems recorded the entire hostname, including the conversation title and random identifier

4

. Claroc researchers dubbed these discoverable pages "GhostShares" because they opened for people who were never handed the link

1

.

Understanding Passive DNS Searches and URL Structure Weaknesses

Passive DNS searches proved instrumental in uncovering the sensitive information exposed through Meta Muse. These commercial services store historical resolution of domain names to IP addresses, collecting DNS responses from sensors at recursive DNS resolvers

1

. A passive DNS record gets created when monitoring systems observe DNS responses, essentially creating searchable databases of every domain lookup

2

.

Claroc queried a commercial passive DNS dataset for Muse's content domain and identified over 6,800 share hostnames after filtering scanning activity

4

. The URL structure weakness meant conversation titles revealed subject matter before researchers even opened pages

4

. Researchers needed only ordinary browsers to view content, with conversations loading through JavaScript even in logged-out incognito sessions

4

.

Meta's Response and Bug Bounty Program Reporting

Asaf Aprozper, Claroc's co-founder and CTO, reported the findings through Meta's bug bounty program on October 8 and attempted to reach Meta staff on LinkedIn without receiving replies

2

5

. Meta issued a statement saying "we've paused this functionality while we review this report and consider changes to how these links can be discovered"

2

3

.

David Singleton, who works on Muse at Meta, announced the fix on Thursday, stating Meta disabled sharing immediately after publication

5

. Artifacts shared before the fix received new web addresses, with old links displaying notes asking users to obtain updated ones

5

. Singleton thanked researchers and noted Muse's bug bounty program pays up to $300,000 for valid findings

5

. When Claroc retested 40 shares on October 20, none remained accessible, though conversation titles persist in passive DNS history

4

5

.

AI Trustworthiness Questions and Previous Zero-Day Vulnerability

This data exposure raises serious questions about AI trustworthiness for Meta Muse, which CEO Mark Zuckerberg claimed was "built from the ground up for privacy and security"

1

2

. The assistant autonomously fills out forms, books appointments, makes purchases, and creates documents, requiring access to most user accounts

1

2

.

Three weeks after launch, macOS security expert Patrick Wardle discovered a zero-day vulnerability allowing any app on the same device to gain complete control of user Muse accounts

1

. Meta downplayed severity, claiming exploitation required compromised devices, without acknowledging that simple ClickFix attacks could hijack accounts

1

. On Wednesday's third-quarter earnings call, Zuckerberg said more than 10 million people had set up Muse, citing email and calendar connections as evidence users trusted its security setup

5

. The combination of this DNS leak with the earlier zero-day vulnerability challenges whether user data protection measures justify the extraordinary access Muse requires.

© 2026 TheOutpost.AI All rights reserved