OWASP Top 10 for LLM Applications
Understand the security risks that can affect LLM-powered applications and the controls organizations can use to protect models, data, applications, and connected systems.

What Is the OWASP Top 10 for LLM Applications?
The OWASP Top 10 for Large Language Model Applications is a community-driven security resource developed by the OWASP GenAI Security Project to identify and address critical security risks in applications powered by large language models and generative AI.
The project was created as LLMs became increasingly embedded in applications, business processes, and enterprise workflows. Its purpose is to help developers, security teams, architects, and organizations understand how AI-specific vulnerabilities can affect applications and how those risks can be mitigated.
The current release is the OWASP GenAI LLM Top 10 2026, published in August 2026. The project has evolved from the original 2023 list into a broader GenAI security initiative covering LLMs, generative AI, and agentic AI systems.
Unlike regulations such as GDPR or the EU AI Act, the OWASP Top 10 is not a law, certification, or mandatory compliance standard. It is security guidance that organizations can use to identify vulnerabilities, establish security controls, and strengthen the development and operation of LLM applications.
What Does the OWASP LLM Top 10 Cover?
The OWASP Top 10 identifies critical security risks associated with LLM and generative AI applications. The categories cover risks across application inputs, models, data, outputs, connected systems, and runtime operations.
Prompt Injection
Malicious or unintended instructions that manipulate an LLM's behavior, potentially causing data disclosure, unauthorized actions, or compromised decisions.
Sensitive Information Disclosure
Exposure of personal, confidential, proprietary, credential, or other sensitive information through LLM interactions and application behavior.
Supply Chain
Security risks introduced through third-party models, datasets, plugins, libraries, services, and other components in the LLM supply chain.
Data & Model Poisoning
Manipulation of training, fine-tuning, or embedding data that can introduce vulnerabilities, backdoors, bias, or unintended model behavior.
Improper Output Handling
Failure to properly validate, sanitize, or control LLM-generated output before it reaches downstream applications or systems.
Excessive Agency
Risks created when LLM applications have excessive permissions or autonomy to perform actions through connected tools and systems.
System Prompt Leakage
Exposure of system prompts, hidden instructions, or other information developers intended to keep from users or attackers.
Vector & Embedding Weaknesses
Security weaknesses in vector databases, embeddings, and Retrieval-Augmented Generation systems that can affect data isolation, retrieval integrity, and model behavior.
Misinformation
Generation or propagation of false, misleading, or unreliable information that can create security, operational, legal, or reputational risks.
Unbounded Consumption
Excessive or uncontrolled consumption of model resources that can lead to denial of service, unexpected costs, degraded availability, or resource exhaustion.
OWASP LLM Top 10 at a Glance
Get a quick overview of the OWASP LLM Top 10, including its scope, current release, and core security focus. Understand how the framework helps identify and mitigate risks across LLM-powered applications and AI workflows.
Who Should Consider the OWASP LLM Top 10?
The OWASP LLM Top 10 is relevant to organizations developing, deploying, integrating, or securing LLM-powered applications.
AI Developers
Teams building applications powered by LLMs, generative AI models, RAG pipelines, or AI agents.
Application Security Teams
Security teams responsible for identifying vulnerabilities in AI-enabled applications and integrating AI security into existing AppSec programs.
AI & ML Teams
Teams developing, fine-tuning, evaluating, deploying, or maintaining models and AI systems.
Enterprise AI Teams
Organizations introducing copilots, AI assistants, internal LLM applications, or generative AI into business workflows.
DevSecOps & Engineering Teams
Teams responsible for securing AI applications throughout development, deployment, and production.
Security & Risk Leaders
CISOs, security architects, AI security teams, and risk leaders establishing controls for enterprise AI adoption.
LLM Security Readiness Checklist
How OWASP LLM Top 10 Fits Into the AI Security Landscape
The OWASP LLM Top 10 can complement broader AI governance, risk, security, and compliance frameworks.

NIST AI RMF
NIST AI RMF provides a broader approach to AI risk management through Govern, Map, Measure, and Manage. OWASP provides more focused security guidance for vulnerabilities specific to LLM and generative AI applications.
ISO/IEC 42001
ISO/IEC 42001 establishes requirements for an Artificial Intelligence Management System. OWASP LLM Top 10 can provide technical security considerations that support an organization's broader AI governance and risk-management program.
EU AI Act
The EU AI Act establishes legally binding requirements for AI systems within its scope. OWASP LLM Top 10 is not a regulatory framework, but its security guidance can help organizations address technical risks relevant to AI security and risk management.
MITRE ATLAS
MITRE ATLAS provides a knowledge base of adversary tactics and techniques targeting AI-enabled systems. OWASP focuses on application vulnerabilities and mitigation guidance, while ATLAS provides an attacker-oriented view of AI threats.
OWASP Top 10 for Agentic Applications
As LLM applications increasingly gain autonomy and access to external tools, agentic AI introduces additional security concerns. OWASP now maintains dedicated guidance for agentic applications, complementing the LLM Top 10 with risks around agent goals, tool use, identity, memory, and autonomous actions.
Frequently Asked Questions
Official OWASP Resources
For authoritative information and community resources about the OWASP Top 10 for Large Language Model Applications, refer to official OWASP documentation: