Meta is suspending Muse’s conversation-sharing feature after researchers found sensitive shared pages through passive DNS. Previously accessible pages stopped opening in a new check, although their hostnames and readable conversation titles remain in historical DNS data. Claroc says it found no evidence that anyone misused the exposed shares.
Meta is suspending conversation sharing in Muse, its task-running AI assistant, while investigating the feature’s privacy. Researchers at security company Claroc found shared conversations through passive Domain Name System (DNS) data. A new check on 20 October found that 40 previously accessible shares no longer opened. The original investigation appeared on 18 October.[1], [2]
When a user asked Muse to share a conversation, it created a page accessible to anyone with its link. Its hostname combined a readable conversation title, a random identifier and the shared-content domain. Opening that link generated a DNS lookup, which passive-DNS services could observe and preserve. Historical entries still contain those hostnames and titles after access to the content stops.[1]
Claroc says it identified more than 6,800 sharing hostnames in one commercial dataset after removing scanning noise, then opened only a few hundred. Almost every accessible shared conversation opened without an account. The researchers stopped at a page requiring a password. More than 75 saved scans of Muse shares also appeared on urlscan.io, a service that stores website scans.[1]
The exposed examples included interview preparation, a company revenue review, a loan application, partial bank details and an employee vacation calendar. Claroc withheld identifying titles and links. It notified Meta’s bug-bounty programme on 8 October, after content checks on 7 and 8 October. One page was reopened on 18 October for a redacted screenshot. The firm says it has no evidence of misuse; its investigation covers one product and discovery channel over a short period.[1]
