SDSignal Desk

Meta’s Muse share links leaked chat titles into public DNS, and researchers found 6,800 of them

· Updated · Signal Desk newsroom

Analysis of reporting by The Verge. How we work

Image: The Verge

Meta paused Muse conversation sharing after Claroc found more than 6,800 share links through public DNS records, some exposing loan applications and revenue reviews. A random ID only protects a link if it isn’t published.

Key takeaways

  • Security firm Claroc found more than 6,800 Muse share links via public DNS records and could open hundreds of conversations.
  • Exposed examples included a revenue review, a loan application, a full-year staff calendar and a job candidate’s interview notes.
  • Per Claroc, each shared page’s address was built from the conversation title plus a random ID, so the hostname in DNS was enough to rebuild the link.
  • Meta paused the feature while it reviews the report; it hasn’t said whether already-exposed links will be invalidated.

What happened

Meta has paused the feature that lets people share Muse conversations by link after security firm Claroc reported finding more than 6,800 of those links in public DNS records. Claroc says it could open hundreds of shared conversations, including a marketing company’s revenue review, a small business owner’s loan application, a workplace’s full-year staff calendar and a job candidate’s notes for a call with an AI lab. Muse spokesperson Tracy Clayton told The Verge that Meta paused the function while it reviews the report and considers how the links can be discovered. Ars Technica first reported the exposure.

How the links leaked

According to Claroc, Muse built each shared page’s web address from the conversation title followed by a random ID. The hostname often revealed what a page contained before anyone opened it, and because the link carried the same title and ID, pulling the hostname from DNS was enough to rebuild it. Public DNS records work as a directory of hostnames, and services that create a unique hostname for each piece of shared content can list them there without meaning to.

A random ID is supposed to make a link unguessable. Putting it somewhere that gets recorded publicly undoes that. Sharing a useful chat with a colleague is a reasonable feature; the failure is treating a share link as private while publishing the clues to find it. A company deploying an assistant to a huge user base should catch that in design review, not after outside researchers do.

A recurring industry failure

The Verge notes that ChatGPT, Claude and Grok conversations have each ended up in Google Search at various points. The industry keeps relearning the lesson: people put business plans, finances and personal lives into these chats, so every sharing pathway should be designed as if the content were sensitive, because it usually is.

For Muse, this adds to earlier trouble, including a Mac zero-day that let local apps hijack the agent (our coverage) and criticism that it nudges users toward sharing more data (review). Meta says Muse now has over 10 million users, with shopping a top activity (coverage), so the exposure surface is large. Trust in an assistant that does work for people rests on dull defaults: links that stay unguessable, clear warnings about what becomes visible and easy revocation.

Why it gets more serious

As assistants handle more real work, chat leaks stop being embarrassing and become material, with financial data, hiring information and internal schedules involved. That raises the bar for every lab shipping share features. The key question for Meta is whether its fix covers links already exposed, not just future ones. Meta’s newer Spaces collaboration feature for Muse makes the same design questions more pressing (Spaces coverage). More in our Meta coverage and cybersecurity coverage.

Who feels it

Muse users
Anyone who created a share link should assume that conversation was discoverable.
Businesses
Employees using consumer assistants for revenue reviews, loans and schedules can leak company data through sharing.
AI companies
Share-link design is a recurring failure point that deserves the same review as login and storage.

What to watch

  1. Whether Meta invalidates links already exposed.
  2. How Meta redesigns share link addresses before restoring the feature.
  3. Notifications to users whose conversations were accessed.
  4. Interest from EU or US privacy regulators.

FAQ

Were Meta Muse conversations exposed?

Yes. Claroc found more than 6,800 Muse share links through public DNS records and could open hundreds of shared conversations.

Is Muse sharing turned off?

Meta paused the share-link feature while it reviews Claroc’s report.

What should Muse users do?

Assume any conversation shared by link may have been discoverable, and avoid sharing sensitive chats until Meta explains its fix.

Read the original

Continue at the source.

The Verge

Companies: Meta

More on Meta

All Meta coverage →