Fetching from the wire…
Public story · 2026-09-10 · high
The test ran 120 adversarial scenarios per domain on four base models, and agent-behavior vulnerability reached 85%.
Why now: The paper posted in September 2026, giving builders running CrewAI or AutoGen a fresh public number for agent-to-agent privacy risk.
Red teams testing CrewAI and AutoGen scored 65% privacy risk in multi-agent configurations, per a paper posted to arXiv.
That number matters for anyone wiring agents together to move data between them. Standard chat-safety testing doesn't check what happens when one agent's output becomes another agent's input.
The test needed only a basic system description to run. It draws on a seven-domain risk taxonomy, generating 120 automated adversarial scenarios per domain, then scoring them with an LLM judge validated by humans. Across four base models, average governance risk came in at 56.25%. Agent-behavior vulnerability, meaning the agents acting on adversarial prompts rather than just leaking data passively, reached 85%.
A single chatbot has one input and one output, and existing red-team tools already cover it. Add a second agent and a data path opens between them that single-turn chat evaluation never touches. Information one agent shouldn't disclose can move to a second agent that has no reason to withhold it, since nobody designed a boundary between them.
The paper doesn't break out which of the seven risk domains drove the governance score versus the behavior score. It also doesn't say whether either framework has since patched specific scenarios, or whether the 65% figure holds across newer model versions.
Each link below shares sources, entities, or timing with this story.
github.com/luckyPipewrench/pipelock — All-in-one security harness with 9-layer scanner pipeline: DLP, SSRF, bidirectional MCP scanning, tool poisoning detection. Zero code changes — agents use it as system proxy. Works with Claude Code, Cursor, CrewAI, LangGraph, AutoGen.
LangChain, LangGraph, CrewAI, AutoGen, Microsoft Agent Framework, and Google ADK, presented at Black Hat (The Register). Insecure deserialization, SSRF, path traversal, use-after-free. That's the point: prompt-controlled content crosses into trusted framework logic, and then i...
After 20+ years maintaining Paint.NET, Rick Brewster concluded WINE's Direct2D would never be complete enough for what he needed, so the app now carries its own from-scratch reverse-engineered Direct2D implementation. He puts it at 180,000 lines against 700,000 for the rest of...
Two thirds. Not two thirds of a contrived jailbreak set. Two thirds of realistic malicious issue requests, against the exact three tools most of the people reading this run daily. Ankur Singh, Jinqiu Yang, and Tse-Hsun Chen built IssueTrojanBench across four attack categories...
Rolling out from June 13, GA June 15, an orchestrator agent inspects registered specialist subagents, reads their descriptions and actions, and routes work using the new Atlas Reasoning Engine 3.0 while preserving context, with A2A and MCP support. Source: Salesforce The patte...
Version bumps are usually boring. This one isn't, because of what it concedes. The OpenAI Agents SDK hit v0.13 with an any-LLM adapter, breaking the assumption that you'd be running OpenAI models inside OpenAI's framework. Requesty's SDK comparison has the details: alongside t...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.