Meta’s Muse publishes a shared conversation as a web page that anyone with the link can open. What made those pages findable to strangers was a naming decision: Muse writes the conversation’s own title into the page’s web address, in the hostname in front of cf.metaaiusercontent.com. Passive-DNS services record hostnames they see in lookups and keep them searchable, so each share left a public DNS record carrying its title. Claroc, the security firm that found the pattern, searched one commercial passive-DNS dataset for that domain and counted more than 6,800 Muse share hostnames. On 20 October 2026 Meta told Ars Technica it has paused the feature while it reviews the report.

This is a different story from the site’s existing Muse Wonder article, which examined Meta’s first frontier model and its memory claims against third-party benchmarks. The subject here is the assistant’s share-link design and who else could find what it published. Nobody broke in, and no misuse of these shares has been shown. Every page was public because its owner asked Muse to share it.

How the conversation title in the hostname made each share findable

The page a person opens sits at muse.ai/s/, with the conversation title and a random ID in its slug. The DNS surface is separate: each share also gets a hostname under cf.metaaiusercontent.com, which passive DNS recorded and the researchers enumerated.

When someone opened a share, their browser looked up the hostname and a passive-DNS provider kept the record. The random ID never had to be guessed. As Claroc put it, “An ID only works as a secret while it stays secret, and a hostname is not a secret.” Finding the shares took one query.

Claroc also noted that urlscan.io, a public scanning service, held more than 75 saved scans of Muse share pages, and a query of the same service on 22 October 2026 returned 85 results, each listed under its page title. Muse’s robots.txt asks most crawlers to stay off the share path. Crawling rules do not control access, and the discovery never involved a search engine.

What Claroc found in the shares, and what Meta says now

Claroc opened a few hundred shares and left the rest. Most were harmless; a minority were not, and every severity call came from a person reading the page. Among those were a candidate’s confidential preparation for an executive-search call with a frontier AI lab, naming the lab’s internal contact and the meeting time; an internal revenue review marked for a company’s CEO; and a small-business loan application stating the amount requested.

Claroc reported the finding to Meta’s bug bounty programme on 8 October and published its write-up, titled “GhostShares”, on 18 October 2026, updating it two days later. Asaf Aprozper, Claroc’s co-founder and CTO, also tried to reach people at Meta on LinkedIn and got no reply. Meta answered Ars Technica instead, saying it had “paused this functionality while we review this report and consider changes to how these links can be discovered.”

That is a pause under review rather than a fix, and Meta has not said the title-in-hostname design changed. Claroc re-checked 40 shares on 20 October and none opened, though the hostnames, titles included, remain in passive-DNS history. Mark Zuckerberg had described Muse in September as “built from the ground up for privacy and security”; Meta’s own engineering post on the assistant notes that Muse “will sometimes make mistakes”. The September ClickFix zero-day is a different matter, a local-app account takeover that Meta patched after Ars reported it.

The 6,800 figure counts share hostnames in one dataset

Claroc counted hostnames in one commercial passive-DNS provider’s data, matching one hostname pattern, on one product, over a short window, after wildcard scan noise was filtered out. Claroc says the figure is not a measure of Muse’s total exposure. A hostname is not a user, and the data cannot show how long a share was reachable or who saw it first.

The examples come from the firm’s own reading of a few hundred pages, and Claroc sells a product that detects reachable AI share links. Ars Technica reports the figure and the examples rather than verifying them independently. Meta has not said whether the pause is temporary, whether the design will change, or whether anyone affected was notified.

What to change if your team uses consumer assistants for work

Treat a share link as a public web page, because that is what it is. On Muse, the conversation title became part of the address that third parties recorded.

Before anyone shares a conversation for work, the usual exclusions apply: client and candidate names, deal terms, loan figures, meeting times with named contacts, staff schedules. If it would not go on a public page, it does not belong in a share link.

Decide where share links may travel, since a link pasted into a channel, a ticket or an external email has the same reach as the original. Put share links in your AI usage guidance alongside approved tools and data rules: who may share, what may be shared, who reviews it, and what to do if a link turns out to be findable. Check the current state of Muse sharing before relying on it; Meta is still reviewing the feature.