
What happened
AI agents—autonomous software systems that make decisions independently—carry distinct security risks because they behave unpredictably, act without waiting for human approval, and can be manipulated over time. Real incidents include Microsoft 365 Copilot's EchoLeak flaw (CVE-2025-32711, CVSS 9.3), Meta's AI assistant being tricked into resetting Instagram passwords for high-profile accounts, and Supabase's database tokens being leaked via a support chatbot.
Why it matters
Unlike traditional software that executes preset instructions, AI agents chain actions together autonomously, so a single error cascades into larger damage before anyone notices. Companies adopting AI agents without proper safeguards face data breaches, unauthorized financial transfers, and account takeovers. The risks are concrete and documented, not hypothetical.
What to watch
Start by restricting agent permissions to only what each task needs, require human approval for high-risk operations (payments, data deletion, external sends), and log all agent behavior to catch anomalies early. Frameworks like OWASP's Agentic AI Threats and Mitigations, Japan's AI Business Operator Guidelines (updated to v1.2 on 31 March 2026), and the EU AI Act all spell out how to build safe AI agent environments.
Summaries like this, every morning.
AI agents differ fundamentally from traditional software because they operate autonomously—once given a goal, they assemble and execute their own steps without waiting for human approval, and they adjust their behavior based on past interactions and external data. This autonomy introduces three categories of risk. First, their outputs are non-deterministic: the same instruction produces different actions each time, so testing cannot guarantee safe production behavior. Second, errors cascade: a single wrong decision propagates through subsequent autonomous actions before anyone can intervene. Third, their adaptability can be weaponized: attackers can gradually adjust inputs to steer the agent toward harmful outputs.
The three concrete incidents—EchoLeak, Instagram account takeover, and Supabase token leakage—all exploit the gap between what developers intended and what an autonomous system does when given ambiguous or malicious input. In each case, traditional security controls (firewall rules, authentication checks) failed because the agent held legitimate permissions and the harmful action looked like a valid task from the agent's perspective. This is why the article emphasizes that agency itself is the vulnerability: power concentrated in an autonomous system magnifies the impact of any mistake or exploit.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
SORACOM's Makoto Yazaki trained Wisora on its own service and documentation pages, then asked how to register…

A solo entrant finished 67th of 6,299 teams in Kaggle's RSNA Knee Abnormality Detection contest, scoring a Pri…

The blogger ordered a used Fujitsu LIFEBOOK U938 for 15,800円 but received a U939 with a Core i5-8365U, 8GB RAM…

A Zenn post lays out five steps for rewriting AI-generated technical drafts, starting by pasting terminal logs…

From late October, the developer sent bounded implementation and research tasks through OpenCode's HTTP API to…

Shane Melaugh analyzed about 1,400 Claude Code sessions with Gemini 4 Argon and found the share of sentences s…
