News

First Known Zero-Click AI Exploit: Microsoft 365 Copilot’s ‘EchoLeak’ Flaw
Security researchers uncovered “EchoLeak,” a zero-click flaw in Microsoft 365 Copilot, exposing sensitive data without user ...
ET CIO3d
The silent threat in your AI stack: Why EchoLeak is a wake-up call for CXOs
Discover the silent threat of EchoLeak, a new vulnerability in AI systems that can lead to data leakage without user ...
SecurityWeek4d
‘EchoLeak’ AI Attack Enabled Theft of Sensitive Data via Microsoft 365 Copilot
Microsoft recently patched CVE-2025-32711, a vulnerability that could have been used for zero-click attacks to steal data ...
Zero-click AI data leak flaw uncovered in Microsoft 365 Copilot
A new attack dubbed 'EchoLeak' is the first known zero-click AI vulnerability that enables attackers to exfiltrate sensitive ...
The Hacker News4d
Zero-Click AI Vulnerability Exposes Microsoft 365 Copilot Data Without User Interaction
Critical zero-click AI vulnerability EchoLeak exposed sensitive Microsoft 365 Copilot data; Microsoft patched it to prevent ...
Microsoft fixes first known zero-click attack on an AI agent
EchoLeak affected Microsoft 365 Copilot, the AI assistant integrated across several Office applications, including Word, ...
Explore more
Microsoft 365 Copilot Vulnerable to Zero-Click EchoLeak Exploit, Cybersecurity Researchers Say
For example, Copilot being able to connect to OneDrive and retrieving data from a file stored there to answer a user query would be considered an agentic action. As per the researchers, the attack was ...
Microsoft 365 Copilot’s Data Exposed – Hit by Zero-Click Vulnerability
Security researchers at Aim Security discovered "EchoLeak", the first known zero-click artificial intelligence (AI) ...
GIGAZINE6d
A zero-click attack method 'Echoleak' that sends emails to manipulate AI and steal confidential information has been discovered, and there is a risk to all AI systems such as ...
Aim Security named the attack method it discovered 'Echoleak' and reported it to Microsoft in January 2025. Microsoft attempted to address the attack in April 2025, but a new problem arose in May ...