US — The Verge

Meta turns Muse sharing back on

SecurityOctober 23, 20261 min read

Meta has turned sharing back on for its Muse AI tool. It had paused sharing after security researchers found that some shared conversations could be easily found online.

Meta turns sharing back on

Meta paused sharing for Muse, its AI agent tool, after security researchers said public links to shared conversations were easy to find. Meta says the problem is now fixed and sharing is working again. The problem was with links to shared Muse artifacts, which are things like documents and images made inside Muse. It was not a problem with chat sharing.

Key facts

Researchers at Claroc found that Muse links were named after each conversation's title and written into public DNS.
Researchers said they could find pages such as a marketing company's internal revenue review and a small business owner's loan application.
Ars Technica reported on Tuesday that Meta paused sharing after it was contacted about the problem.
10 million people have already set up Muse agents, according to a related story from The Verge.

What went wrong

DNS is the system that turns web addresses into the numbers computers use to find websites. If a link is written into public DNS, it can be found by others. Here, the web addresses were based on conversation titles, which made them easy to guess or find.

Why it matters

Private business documents, such as a revenue review and a loan application, were reachable by people who should not see them. Meta says protecting user data must come first, even though the fix means some people must get new links.

What to watch

People with old artifact links will see a note asking them to get a new link from the person who shared it.
Whether Meta explains more about how the problem happened and how it will prevent similar issues.
Whether security researchers confirm that the fix works.

Glossary

Muse: Meta's AI agent tool that can chat and make things like documents and images.
Claroc: A security research group that reported the problem with public Muse links.
DNS: The system that connects web addresses to the computer locations where websites live.
Ars Technica: A technology news website that reported on Meta pausing Muse sharing.

Same story, different eyes

The EngineerAI

A fix that changes every shared link, on purpose

From an engineer's seat, what stands out is that the fix meant giving every shared artifact a brand-new URL, so old links now show a note asking people to get the new one. That's a bit annoying for users, but it's the clean way to make sure the old, easy-to-find addresses stop working. Titles being used in public DNS names looks like a small design choice that grows into a big exposure, which is a good reminder of how much care even a naming scheme needs. How Meta decided what to change in the new link format hasn't been shared yet.

The SkepticAI

One new link per shared file is the real fix to check

Meta says the problem was in the URLs for shared artifacts like documents and images, and that old links now point to a notice and each artifact has a new URL. That's a reassuring sign, since it suggests the old addresses were actually retired. It would be even more convincing to see an independent check, maybe from the Claroc researchers, that the new links can't be guessed or found through public DNS the way the old ones could. How many shared artifacts were reachable before the fix is not yet known.

The UserAI

Muse sharing is back, but your old links just changed

If you've shared a Muse document or image at work, the practical change is that the old link now shows a note asking people to get a new one from you. So it's worth re-sending those links to teammates or clients, and it's a good moment to think about what you've been putting into shared artifacts. Sharing is already back on, so you should be able to feel the difference right away. How many shared pages were actually found by outsiders hasn't been shared yet.

Tioli Releases Emergency Response Guide for 'Node2Shell'

Tioli said on the 26th that it had independently reproduced and verified the Node.js vulnerability 'Node2Shell (CVE-2026-111497)', disclosed on the 21st, and published a response guide. The flaw stems from a memory-handling error when decompressing Brotli-compressed data, and Node.js rates its severity as High. Patched versions 22.23.4, 24.22.1, and 26.12.1 were released.

Security전자신문Oct 26

Logpresso Releases 'PHP2Shell Scanner' to Check Internal Network Vulnerabilities

Logpresso has released a 'PHP2Shell Scanner' app that diagnoses the PHP remote code execution vulnerabilities known as PHP2Shell. The tool can scan both publicly exposed websites and PHP-based systems on internal networks, where internet-based scanning services cannot reach.

SecurityVnExpressOct 26

The Privacy Risks of "Always-Listening" AI Devices

AI-enabled devices such as smart speakers, smartwatches and smart glasses that are always ready to respond can collect data, raising privacy concerns. Global shipments of AI glasses reportedly jumped to 8.4 million in 2025 from 2.1 million in 2024, according to Omdia data cited by Reuters. Experts warn that bystanders may be monitored without owning any device, and that AI can interpret far more collected information than earlier voice assistants.