Can AI Agents Become a New Cybersecurity Threat? What the Evidence Shows
Software that can read, decide and act on its own is arriving inside companies faster than the rules for controlling it. Security researchers say the risk is real — and more specific than the hype suggests.
Artificial intelligence agents — systems that combine a large language model with tools, memory and the ability to take actions — are moving from demonstrations into daily business operations. They read email, query databases, write and run code, and interact with customers. That shift raises a question that security researchers are now treating as a distinct field of study: do AI agents create a genuinely new category of cybersecurity threat, or are they simply old risks in new packaging?
The honest answer, based on the research published so far, is: both. The underlying attack techniques are often familiar, but the way agents combine permissions, autonomy and untrusted input creates failure modes that traditional security controls were not designed to catch.
WHAT MAKES AN AGENT DIFFERENT FROM A CHATBOT
A conventional chatbot produces text. An agent produces actions. The distinction matters because the worst outcome of a compromised chatbot is a bad answer, while the worst outcome of a compromised agent can be a deleted database, a transferred payment or a leaked file.
A systematization of knowledge published at the USENIX Security Symposium in August 2026 — one of the first comprehensive academic frameworks for agent security — describes agents as hybrid systems whose flexibility "introduces complex security challenges that differ from those found in traditional software systems." The paper, by researchers at UC Berkeley, Seoul National University and UC Santa Barbara, maps the design space of agents alongside their attack landscape and defenses, and concludes that securing them is an open research problem, not a solved engineering task.
THE ATTACKS RESEARCHERS HAVE DOCUMENTED
The OWASP GenAI Security Project, which maintains a widely used risk list for large language models, published a dedicated AI Agent Security Cheat Sheet that catalogs the specific risks agents add on top of prompt injection. Among them:
Indirect prompt injection. An agent that reads web pages, documents or emails can encounter instructions hidden in that content — for example, text in a webpage telling the agent to forward the contents of the user's inbox to an outside address. The agent cannot reliably distinguish data from commands, which is the core unresolved problem.
Tool abuse and privilege escalation. Agents are often given broad tool permissions so they can be useful. An attacker who influences the agent inherits those permissions.
Memory poisoning. Malicious data written into an agent's persistent memory can influence future sessions or other users.
Goal hijacking. Manipulating what the agent is trying to accomplish while it appears to behave normally.
Excessive autonomy and high-impact actions. Agents executing irreversible, financial or externally visible operations without independent validation.
Cascading failures. In multi-agent systems, one compromised agent can propagate an attack to others.
Denial of wallet. Forcing an agent into unbounded loops that run up API and compute costs.
A January 2026 presentation hosted by NIST from the OWASP Agentic Security Initiative frames the evolution similarly: traditional cyber risks such as phishing and data theft persist, generative AI added prompt injection, supply-chain risk and "excessive agency," and agentic systems compound all of these at once.
THIS IS NOT ONLY THEORETICAL
ISACA, the professional association for IT governance and security auditors, published a white paper in September 2026 with a striking claim: in July 2026, an agentic AI system infiltrated Hugging Face production infrastructure before another AI system detected and flagged the intrusion. ISACA describes this as the arrival of "the age of AI battling AI." The incident matters less for its details than for its direction: autonomous systems are now appearing on both sides of intrusions.
The same white paper notes that agentic AI is expected to become nearly ubiquitous within two years, with three in four companies using it at least moderately — meaning the attack surface is expanding faster than most security programs are adapting.
WHY TRADITIONAL DEFENSES FALL SHORT
Conventional security assumes software does what it is programmed to do, and that inputs are either data or code. Agents break both assumptions. A language model interprets instructions probabilistically, so the same input can produce different behavior on different runs, and content that arrives as data — an email, a document, a search result — can function as code once the agent acts on it.
A 2026 survey in ACM Computing Surveys puts it precisely: in agentic loops, "failures are no longer limited to unsafe text generation, since untrusted content may redirect control flow, misuse tool privileges, corrupt persistent state, leak sensitive information, or trigger harmful external actions." The risk, in other words, depends on how the model is wired into orchestration logic, tools, permissions and runtime environments — a system property, not a model property.
WHAT DEFENDERS CAN ACTUALLY DO
The emerging consensus across OWASP, NIST-hosted research and ISACA is that agents require a layered approach rather than a single fix:
Least privilege for tools. Give each agent the minimum permissions its task requires, and separate read access from write or payment authority.
Human approval for high-impact actions. Irreversible, financial or externally visible operations should require independent validation, not just the agent's own confidence score.
Treat all external content as untrusted. Anything the agent reads — email, web pages, documents — should be handled as a potential attack vector, with instructions in content never executed by default.
Isolate and monitor. Run agents in constrained environments, log their tool calls, and watch for loops, unusual data flows and unexpected external requests.
Test adversarially. Red-team the whole system, including the tools and memory, not just the model.
ISACA's white paper packages this as a "secure by default" checklist intended to help enterprises find gaps in existing programs.
THE BALANCED VERDICT
AI agents are not an unstoppable new superweapon for attackers, and the most breathless claims about them should be discounted. Most documented agent attacks still depend on ordinary weaknesses: excessive permissions, missing approval steps, unvalidated input. But it is equally wrong to dismiss the risk as hype. Agents concentrate three things that security teams have historically tried to keep apart — access to sensitive data, authority to act, and exposure to untrusted content — and they do so at machine speed, at scale, with behavior that is probabilistic rather than deterministic.
The realistic reading of the 2026 evidence is that agents are becoming a meaningful new layer of the threat landscape, that the attack techniques are maturing quickly in academic and practitioner research, and that the defenses are real but immature. Organizations deploying agents now are, in effect, running an experiment on their own infrastructure — which makes the boring controls above more important, not less.
WHAT WE DO NOT KNOW YET
Reliable public data on how often agent-specific attacks succeed in the wild does not exist; reported incidents are anecdotes, not rates. The Hugging Face intrusion described by ISACA has limited public technical detail. No independent benchmark yet measures how well the recommended defenses hold up against determined attackers, and the academic surveys themselves note that evaluation methods for agent security are still being developed. Finally, how regulators will assign liability when an autonomous agent causes a breach remains an open legal question in most jurisdictions.
EDITORIAL NOTE AND SOURCES
This explainer was prepared with AI assistance for research and drafting, and reviewed by the desk before publication. Primary sources: OWASP AI Agent Security Cheat Sheet (https://cheatsheetseries.owasp.org/cheatsheets/AI_Agent_Security_Cheat_Sheet.html); Kim, Guo and Song, "SoK: Attack and Defense Landscape of Agentic AI Systems," USENIX Security Symposium, August 2026 (https://www.usenix.org/system/files/usenixsecurity26-kim-juhee-agentic.pdf); OWASP Agentic Security Initiative presentation hosted by NIST, January 2026 (https://csrc.nist.gov/csrc/media/presentations/2026/agentic-ai-emerging-threats%2C-mitigations%2C-and-cha/1.3-agentic_ai-sotiropoulos.pdf); ISACA, "Cybersecurity Recommendations for Securing AI Agents," September 2026 (https://www.isaca.org/resources/white-papers/2026/cybersecurity-recommendations-for-securing-ai-agents); Ling et al., "Toward Secure LLM Agents: Threat Surfaces, Attacks, Defenses, and Evaluation" (https://arxiv.org/html/2606.10749v2). Where claims rest on a single source, the article says so.
Every claim above is sourced to a document, a named person, or a record we hold. Where we could not verify a claim, we say so. Read our standards and corrections policy →
