Shared Claude conversations and Artifacts turned up in Google search, exposing medical records and children's contact details
At a Glance
- Serious damage. Customer data affected, security incident, or financial losses $10k–$100k.
Independent project · aggregated from public reports and may be unverified — see the primary source below · not affiliated with or endorsed by any company or product named.
What Happened
In late July 2026 users found that Claude share links were being indexed by Google and could be surfaced with a site: search operator. Reporting described exposed content including a detailed medical report of a real patient, clinical trial results containing patient names, documents listing the names and phone numbers of primary school-aged children, internal-use-only company documents, and employee reviews containing personal information about workers. Anthropic responded that share links only appear in search results when users post them somewhere search engines can see, and said the links are not guessable or discoverable otherwise. By the Monday afternoon the exposure appeared remediated and searches returned no results.
Case Analysis
Verified Facts
- Claude share links were indexed by Google and discoverable with a site: search operator
- Exposed content included patient medical data, children's names and phone numbers, and internal company documents
- Anthropic said share links only appear in search when users post them publicly; the exposure was remediated within days
Not Publicly Confirmed
- How many conversations were indexed in this incident
- Whether any exposed data was scraped before removal
Operational Lessons
- A share feature that produces a public URL is a publishing feature and must be designed as one
- Sensitive data pasted into an assistant inherits whatever sharing default the product ships with
Primary Source
PSA: Your Claude shared chats and Artifacts may have ended up on Google (TechCrunch)techcrunch.com ↗Case Record
More Cases
Prompt injection reached host-level code execution in Microsoft Semantic Kernel through eval() and a stray annotation
Microsoft disclosed two vulnerabilities that turn prompt injection into host compromise in its Semantic Kernel agent framework, which has over 27,000 GitHub stars. CVE-2026-26030 affects the Python package before 1.39.4: the default in-memory vector store filter is a Python lambda executed with eval() on unsanitized model-controlled input, so an attacker could escape the template string, traverse Python's class hierarchy, bypass the AST blocklist validator and run arbitrary commands, demonstrated by launching calc.exe from a single prompt injection. CVE-2026-25592 affects the .NET SDK before 1.71.0: DownloadFileAsync was accidentally marked with a [KernelFunction] attribute, exposing it to the model with an entirely AI-controlled, unvalidated local file path, allowing writes to locations such as the Windows Startup folder and thus sandbox escape.
Cursor's command allowlist could be bypassed with shell built-ins, giving prompt injection a silent path to code execution
Pillar Security disclosed CVE-2026-22708 in Cursor. In Auto-Run Mode with an allowlist enabled, shell built-ins such as export, typeset, declare, readonly, unset and local were implicitly trusted by Cursor's server-side evaluator and executed without appearing in the allowlist or requiring approval, because they run inside the shell session rather than as separate binaries. An attacker delivering indirect prompt injection could silently poison environment variables and then trigger malicious code through trusted developer tools, producing both zero-click and one-click remote code execution. Pillar reported it in August 2025, Cursor acknowledged it as a systemic issue in September 2025, and the fix shipped in version 2.3 in January 2026, which now requires explicit approval for any command the parser cannot classify.
SearchLeak let a single click on a malicious link pull emails, files and MFA codes out of Microsoft 365 Copilot
Varonis Threat Labs disclosed CVE-2026-42824, a critical flaw in Microsoft 365 Copilot Enterprise Search. Clicking a single crafted link chained three bugs: injection of the URL parameter into the prompt, a rendering race condition, and abuse of Content Security Policy allowlisting to exfiltrate data through Bing's infrastructure. The attack could reach emails and calendar details, indexed SharePoint and OneDrive files, one-time and MFA codes, password-reset links, meeting notes and salary data. Because Copilot Enterprise is a managed service, tenant admins could not patch it themselves; Microsoft mitigated the flaw on its backend.