Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7
Tag: memory-poisoning (2 articles)Clear

Researchers trick Microsoft Copilot into revealing its own data-exfiltration bypass

Varonis disclosed a flaw in Microsoft Copilot Personal, the consumer assistant, that could let a single click exfiltrate data from connected apps, and the way they found it is striking. Tracked as CVE-2026-24301 and named CoSnitch, the technique had the researchers repeatedly ask Copilot why a prompt could not run without user interaction; each refusal added a technical justification, until the assistant named a hidden parameter, the exact session conditions where it worked, and the protections meant to block it. Building the request as described, the bypass ran. Varonis said Copilot was not breached but played. Related research showed attacker pages persisting unwanted memory in Copilot through indirect prompt injection.

Check
Treat AI assistants with access to connected apps and persistent memory as a data-exfiltration and manipulation surface, and review what apps and data your assistants can reach on a single user action.
Affected
Users of AI assistants like Microsoft Copilot Personal connected to email and other apps; a crafted link can drive the assistant to leak connected-app data or persist attacker instructions in its memory.
Fix
Limit which apps and data assistants can access, apply vendor updates, be cautious with links that invoke an assistant, and watch for unexpected actions, since a refusal does not close a bypass.

Ruflo AI agent platform exposed 233 tools through an unauthenticated MCP bridge

Noma Labs found a critical flaw in Ruflo, an open-source platform for orchestrating swarms of AI agents that acts as a harness for coding agents like Claude Code and Codex. Tracked as CVE-2026-59726 and scored 10.0, the flaw is that Ruflo's default Docker deployment exposed its Model Context Protocol bridge to the network with no authentication, offering 233 callable tools. A single unauthenticated request could invoke a shell command tool to run code in the bridge container, read AI provider API keys, steal stored conversations, and poison the platform's persistent agent memory, which can steer future outputs even after the attacker leaves. The flaw is in Ruflo, not in the coding agents.

Check
If you run Ruflo, formerly Claude Flow, update to version 3.16.3 or later, and confirm its MCP bridge is not bound to a network-reachable interface.
Affected
Teams running Ruflo before 3.16.3 with the default Docker deployment (CVE-2026-59726); an unauthenticated network attacker can run commands, steal AI provider keys and conversations, and poison persistent agent memory.
Fix
Update Ruflo, rotate AI provider API keys, rebuild affected containers from clean images, inspect the agent memory store for unfamiliar instructions, and keep MCP bridges bound to loopback and behind authentication.