OWASP Top 10 2025: all 10 categories and what changed since 2021
The OWASP Top 10:2025 list with all 10 categories, the 2021 mapping, two new entries, where SSRF went, and one prevention control for each.
The OWASP Top 10:2025 lists ten categories: Broken Access Control, Security Misconfiguration, Software Supply Chain Failures, Cryptographic Failures, Injection, Insecure Design, Authentication Failures, Software or Data Integrity Failures, Security Logging and Alerting Failures, and Mishandling of Exceptional Conditions. Compared with the 2021 list, there are two new entries (A03, an expansion of the old components category, and A10), SSRF is folded into access control, and Security Misconfiguration climbs from fifth to second place.
This guide gives the full list, a 2021-to-2025 mapping, and a short note on each category. Everything below comes from the official OWASP Top 10:2025 pages and is current as of October 2026.
The OWASP Top 10:2025 list
- A01:2025 Broken Access Control
- A02:2025 Security Misconfiguration
- A03:2025 Software Supply Chain Failures
- A04:2025 Cryptographic Failures
- A05:2025 Injection
- A06:2025 Insecure Design
- A07:2025 Authentication Failures
- A08:2025 Software or Data Integrity Failures
- A09:2025 Security Logging and Alerting Failures
- A10:2025 Mishandling of Exceptional Conditions
The project describes this as the eighth edition of the Top 10. It is an awareness document for developers and security teams, not a standard you can certify against. For testable requirements, OWASP points to the Application Security Verification Standard (ASVS).
How the data was gathered
According to the introduction, the dataset covers more than 2.8 million applications supplied by 13 contributor entries, one of them anonymous, plus several other anonymous donors. It spans 589 CWEs, and the ten categories together contain 248 of them. Ranking combined how many applications had at least one instance of a weakness with exploit and impact scores derived from CVE data. A community survey promoted two categories that the data could not fully capture: A03 and A09.
2021 to 2025: what changed
Here is where each 2021 category went, based on the OWASP mapping:
- Broken Access Control stays at #1 and absorbs A10:2021 Server-Side Request Forgery (SSRF). CWE-918 now sits inside A01.
- Security Misconfiguration moves from #5 to #2.
- Vulnerable and Outdated Components (A06:2021) is expanded into Software Supply Chain Failures at #3.
- Cryptographic Failures drops from #2 to #4.
- Injection drops from #3 to #5.
- Insecure Design drops from #4 to #6.
- Identification and Authentication Failures is renamed Authentication Failures and stays at #7.
- Software and Data Integrity Failures becomes Software or Data Integrity Failures and stays at #8.
- Security Logging and Monitoring Failures becomes Security Logging and Alerting Failures and stays at #9.
- Mishandling of Exceptional Conditions is new at #10.
The ten categories in brief
A01 Broken Access Control
Users can act outside their intended permissions, for example by changing an account number in a URL to read someone else’s record. The category maps to 40 CWEs, including CWE-200, CWE-352 (CSRF) and CWE-918 (SSRF). OWASP reports that every tested application showed some form of it. Key control: deny by default and enforce checks on the server, in one reusable place.
A02 Security Misconfiguration
A system, framework or cloud service is set up insecurely: default credentials, sample apps left on production, open storage, verbose errors. It maps to 16 CWEs, including CWE-16 and CWE-611 (XXE). Key control: a repeatable, automated hardening process, with configuration checks in every environment. Teams running clusters and cloud accounts will recognise this one; see our cloud coverage.
A03 Software Supply Chain Failures
Compromises in how software is built, distributed or updated, including malicious or vulnerable third-party packages. Only six CWEs are mapped and few CVEs carry them (OWASP counts 11), so the community survey, where it was the top-ranked risk, pushed it up. The page cites the 2025 Shai-Hulud npm worm as an example. Key controls: maintain an SBOM that includes transitive dependencies, take components from trusted sources, and harden the build pipeline with separation of duties.
A04 Cryptographic Failures
Missing, weak or badly managed cryptography, such as cleartext transport or weak password hashing. It maps to 32 CWEs, including CWE-327, CWE-319 and CWE-916. Key controls: TLS 1.2 or later with HSTS, a slow salted hash such as Argon2, scrypt or PBKDF2 for passwords, and no hard-coded keys. Certificate lifetimes are shrinking, so see our explainer on the TLS certificate validity schedule.
A05 Injection
Untrusted input reaches an interpreter such as a database, shell or browser and is executed as part of a command. It maps to 37 CWEs, including CWE-89 (SQL injection), CWE-79 (XSS) and CWE-78 (OS command injection), and includes XSS, which alone has more than 30,000 CVEs. Key control: parameterized queries and safe APIs, backed by allowlist validation.
A06 Insecure Design
Flaws in architecture and business logic that perfect code cannot fix. OWASP gives the example of a booking system with no cap on discounted seats. It maps to 39 CWEs, including CWE-434 and CWE-522. Key control: threat modeling of authentication, access control and business flows before building.
A07 Authentication Failures
The system accepts an invalid user as legitimate because of weak passwords, missing MFA or poor session handling. It maps to 36 CWEs, including CWE-287, CWE-384 and CWE-798. Key controls: MFA, throttling of repeated failures, blocking breached passwords, and new session IDs after login.
A08 Software or Data Integrity Failures
Code, updates or data are used without checking that they are trustworthy, for instance deserializing client-supplied state without an integrity check. It maps to 14 CWEs, including CWE-502 and CWE-829. Key control: verify signatures and keep CI/CD pipelines segregated and reviewed.
A09 Security Logging and Alerting Failures
The rename shifts the emphasis from collecting logs to acting on them. A log nobody is alerted about does not stop an attack in progress. Key control: log security-relevant events, such as failed access checks and logins, and route them to alerts someone responds to.
A10 Mishandling of Exceptional Conditions
New in 2025. It covers failing to anticipate, detect or respond to unusual situations, which leads to crashes, information leaks and logic errors. It maps to 24 CWEs, including CWE-209 (error messages exposing sensitive information), CWE-476 (NULL pointer dereference) and CWE-636 (not failing securely). OWASP’s example is a multi-step money transfer interrupted midway and never rolled back. Key controls: handle errors where they occur, add a global handler as a safety net, and fail closed.
What to do with the list
- Update training material. Courses built on 2021 still teach SSRF and “vulnerable components” as separate categories.
- Re-map internal findings. Scanner and pentest reports tagged with 2021 IDs will need translating using the mapping above.
- Add supply chain and error handling to reviews. These are the two areas most teams have no checklist for.
- Use ASVS for requirements. The Top 10 tells you what to worry about; ASVS tells you what to test.
For related reading, browse our vulnerabilities and DevOps tooling sections, or the broader security desk. If you track how fast known exploited bugs must be fixed, see our explainer on CISA BOD 26-04 KEV timelines.
Frequently asked questions
What are the new categories in OWASP Top 10 2025?
There are two: A03 Software Supply Chain Failures, which expands the 2021 components category, and A10 Mishandling of Exceptional Conditions.
What happened to SSRF in the 2025 list?
Server-Side Request Forgery, A10 in 2021, was merged into A01 Broken Access Control. CWE-918 is now one of the CWEs mapped to that category.
Is the OWASP Top 10 a compliance standard?
No. It is an awareness document that ranks common risks. For verifiable security requirements, OWASP recommends the Application Security Verification Standard.
Where can I find the OWASP Top 10 2025 PDF?
The project publishes the list and every category page at top10.owasp.org/2025. Check that site for downloadable formats, since they can change between releases.
Is the OWASP Top 10 2025 based on data?
Mostly. It uses data from more than 2.8 million applications, and a community survey promoted two categories (A03 and A09) that data alone could not rank.