Loading story…
Researchers disclosed CVE-2026-32193, a Microsoft Copilot hijack that abused an undocumented URL parameter, ?autorun=1, to bypass the normal user-approval step and automatically run attacker-supplied prompts. By pairing that parameter with crafted input in the q field, an attacker could make Copilot operate within a victim’s authenticated session, search connected enterprise data including inbox contents, and send sensitive results to an attacker-controlled server. The attack could be delivered through phishing links, chat messages, webpages, or QR codes, and researchers reported it could continue even if the victim closed the Copilot tab immediately after opening it.
Separate reporting tied the issue to a broader attack chain described as moving from an AKS node root vulnerability to a Copilot compromise, underscoring how cloud and AI weaknesses can be chained together. Researchers also described a second prompt-injection method that poisoned Copilot’s persistent memory using hidden webpage metadata, allowing later manipulation of Copilot responses and actions. The disclosures highlight risks from undocumented AI features, prompt injection, and trusted-session abuse in enterprise copilots connected to corporate data.
Track how attackers are adapting to this technology.
4 events from the most recent confirmed update back to the earliest known activity.
Microsoft said it patched the Copilot issue involving the undocumented autorun=1 URL parameter on 18 August, after Varonis had reported the vulnerability in December. The article says the flaw had remained exploitable for about eight months before the fix.
A post on r/netsec linked to an article titled "From AKS node root vulnerability to Microsoft Copilot hijack (CVE-2026-32193)." The provided content does not include technical details, exploitation evidence, or remediation information beyond the title’s association of the CVE with Microsoft Copilot and an AKS node root vulnerability.
Varonis also reported a distinct prompt-injection method that poisoned Copilot’s persistent memory through hidden webpage metadata. According to the report, this could manipulate future outputs and actions, including forwarding outputs, filtering information, or biasing responses toward attacker-chosen narratives.
Varonis described a Microsoft Copilot attack in which an undocumented URL parameter, ?autorun=1, caused prompt instructions supplied in the q parameter to execute automatically without the normal user-approval step. The researchers said a crafted Copilot URL could abuse a victim’s authenticated session to search connected data such as inbox contents and exfiltrate sensitive information to an attacker-controlled server.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
Follow how adversaries are adapting to this technology, and where it touches your stack today.
3 references tracked. Mallory keeps watching after this page renders.
pivot-to-ai.com
Open sourcearstechnica.com
Open sourcereddit.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Security researchers disclosed attacks against Microsoft Copilot that use prompt injection and chained requests to extract sensitive data with minimal user interaction. Varonis Threat Labs described a **single-click** technique called **Reprompt** against **Microsoft Copilot Personal** that abuses legitimate Copilot links with a prefilled `q` parameter, then uses a **double-request** and **chain-request** flow to hide exfiltration instructions on an attacker-controlled server. The report said the attack could continue pulling data from an active session even after the Copilot tab was closed, while evading many client-side monitoring tools; Microsoft said the issue had been patched, and Varonis reported that **Microsoft 365 Copilot enterprise customers were not affected**. A separate report from **Rubrik Zero Labs** said it had **broken the Microsoft 365 Copilot sandbox** in research published under the title *ChatMate*, indicating continued scrutiny of Copilot’s isolation and data-protection boundaries across Microsoft’s AI offerings. Together, the disclosures highlight how trusted Copilot workflows, prefilled prompts, and multi-step prompt handling can be abused to bypass intended safeguards and expose user data, reinforcing the need to treat AI prompt inputs and follow-on actions as untrusted.
Aug 12, 2026
Researchers reported that vulnerabilities in Microsoft 365 Copilot and Consumer Copilot allowed attackers to turn prompt injection into data exfiltration, memory poisoning, and persistent compromise. Microsoft assigned `CVE-2026-24299` to the main issue set and rolled out fixes across late 2025 and early 2026, while a related Microsoft Excel flaw, `CVE-2026-26144`, showed how a conventional application bug could be chained with Copilot Agent mode to silently extract spreadsheet data. In the Copilot attacks, malicious content abused HTML preview rendering to leak sensitive information through external requests, first with CSS background images and later with `@font-face`, and researchers said users could be coerced into triggering the preview during normal interaction, creating a near zero-click exfiltration path. The research also showed that Copilot’s memory features could be poisoned to add or delete stored facts and implant persistent instructions that altered future sessions, enabling a backdoor dubbed **SpAIware** that continued leaking secrets over time. Similar issues were described in consumer Copilot, including durable-memory manipulation and browser-navigation exfiltration through Edge-integrated tooling. The findings underscore a broader security shift: AI assistants can collapse trust boundaries inside host applications, raising the impact of older flaws and forcing defenders to reassess assistant permissions, restrict outbound network access from AI-enabled apps, and separately monitor AI-initiated network activity.
Jun 29, 2026
Security researchers disclosed **Reprompt**, a single-click attack against **Microsoft Copilot Personal** that enabled stealthy exfiltration of sensitive user data by abusing a legitimate Copilot URL containing a malicious `q` parameter. After a victim clicks the link (typically delivered via phishing), the crafted URL triggers **Parameter-to-Prompt (P2P) injection**, auto-executing attacker-controlled prompts within the victim’s authenticated Copilot session; researchers reported the attacker can maintain control and continue querying data even after the Copilot window/tab is closed. Microsoft has **patched** the issue. Varonis Threat Labs described an attack chain that combines three techniques to bypass Copilot’s guardrails and evade detection: **P2P injection** (prompt injection via the `q` parameter on page load), **Double-Request** (leveraging the observation that leak protections may apply to the first request but not a repeated action), and **Chain-Request** (server-driven, sequential follow-up prompts that adapt based on prior responses). Reported exposed data includes **personally identifiable information (PII)** and other Copilot-accessible context such as conversation memory and user details (e.g., location and activity/history), with the staged prompting designed to appear benign while progressively leaking information to attacker-controlled infrastructure.
Jun 29, 2026