Pricing Insights
Book a demo

OWASP Top 10:2025: what changed and what to check

The OWASP Top 10 is a common language for security staff and developers. Below are all ten categories of the 2025 edition in Russian: what each means, what to check and which tools help. In my opinion it is a good working document for understanding the main risks; for deeper understanding, use ASVS.

Source: OWASP Top 10:2025, top10.owasp.org · category names are official; translation and explanations by TRAIO Insights

Checklist

  • Server-side access checks for every object and action (A01)
  • Baseline settings and scanning of IaC and containers (A02)
  • SCA and SBOM on every build (A03)
  • Current TLS, keys in a secrets store (A04)
  • SAST with taint analysis on every pull request (A05)
  • Threat modeling for new features (A06)
  • MFA and brute-force protection (A07)
  • Signed artifacts and updates (A08)
  • Logs and alerts for security events (A09)
  • Fail safely on errors (A10)

What changed compared with 2021

One new category, one expansion, two mergers, two renamings. The main point: the software supply chain became a separate major risk, and configuration errors rose to second place.

  • New category A10:2025 Mishandling of Exceptional Conditions (unsafe handling of exceptional situations).
  • A03:2025 Software Supply Chain Failures is an expansion of the former A06:2021 Vulnerable and Outdated Components: it now covers the whole supply chain, not only outdated libraries.
  • SSRF is no longer a separate category; it is now part of A01:2025 Broken Access Control.
  • Renamed: “Identification and Authentication Failures” → Authentication Failures (A07), “Security Logging and Monitoring Failures” → Security Logging & Alerting Failures (A09).
  • Security Misconfiguration rose from 5th place to 2nd; Cryptographic Failures fell from 2nd to 4th, Injection from 3rd to 5th, Insecure Design from 4th to 6th.
  • The basis is data on more than 2.8 million applications and about 175 thousand CVE records mapped to CWE; two categories (A03 and A09) were raised based on a community survey.

A01:2025 Broken Access Control

A user gets access to other people's data or functions: swaps an identifier in a request, calls an admin API method, bypasses a permission check. First place since 2021. SSRF is now included here too: the server calls an address supplied by the attacker.

  • Check permissions on the server for every object and action, not only by hiding buttons in the interface.
  • Deny by default, grant access explicitly.
  • Tests for identifier substitution (IDOR/BOLA) in the API.
  • Limit the server's outgoing requests (SSRF protection).

A02:2025 Security Misconfiguration

Open admin panels, default passwords, verbose errors with stack traces, unneeded services, public buckets. It rose to second place: there is more configuration now, with clouds, containers and Kubernetes.

  • Strict baseline settings and identical environments through infrastructure as code.
  • Scanning of IaC and container images in CI.
  • Turn off debugging and verbose errors in production.

A03:2025 Software Supply Chain Failures

Vulnerable and malicious dependencies, compromised build tools, substituted packages. An expanded version of the former category on outdated components.

  • SCA on every build and an SBOM for every version.
  • A package proxy repository and blocking of dangerous versions.
  • Pinned versions, integrity checks and CI/CD protection.

A04:2025 Cryptographic Failures

Data without encryption, outdated algorithms and protocols, keys in code, predictable random numbers.

  • A current TLS version on all connections.
  • Modern algorithms and proven libraries, no home-made cryptography.
  • Keys in a secrets store, not in code.

A05:2025 Injection

SQL, OS command, LDAP, XSS and others: unchecked data reaches an interpreter. It fell to fifth place thanks to frameworks, but is still very common.

  • Parameterized queries and ORM.
  • Output encoding in templates.
  • SAST with taint analysis on every pull request.

A06:2025 Insecure Design

Errors in the logic and architecture itself that a line of code cannot fix: no limits on attempts, a business process that can be bypassed, trust in client data.

  • Threat modeling at the design stage.
  • Security requirements from ASVS in tasks.
  • Tests for abuse of business logic.

A07:2025 Authentication Failures

Weak passwords, no brute-force protection, errors in sessions and access recovery, no second factor where it is needed.

  • Multi-factor authentication for critical operations.
  • Attempt limits and brute-force protection.
  • Safe session management and password recovery.

A08:2025 Software or Data Integrity Failures

Updates and data are accepted without an integrity check: insecure deserialization, unsigned updates, trust in third-party scripts.

  • Signing and verification of artifacts and updates.
  • Avoid insecure deserialization.
  • Integrity control of third-party scripts on pages.

A09:2025 Security Logging & Alerting Failures

The attack is not visible: important events are not logged or nobody reacts to them. The new edition stresses alerts: a log without an alert does not help.

  • Logging of logins, access denials and critical operations.
  • Alerts on suspicious events and a clear response process.
  • Protection of logs from modification.

A10:2025 Mishandling of Exceptional Conditions

A new category: the application behaves wrongly on errors and abnormal situations. It reveals too much in error messages, “fails open” instead of closing, or leaves the system in an inconsistent state.

  • Fail safe: on error, deny rather than allow.
  • Error messages without internal details.
  • Tests for boundary and erroneous input data, fuzzing.

Questions and answers

What is the OWASP Top 10?

A regularly updated list of the ten most critical web application security risks from the OWASP community. The current edition is from 2025.

What is new in OWASP Top 10:2025?

New category A10, unsafe handling of exceptional situations; A03, software supply chain failures (an expansion of the former category on outdated components); SSRF moved into A01; configuration errors rose to second place.

How does the OWASP Top 10 differ from ASVS?

The Top 10 is the ten main web application risks and a common language for security staff and developers. ASVS goes deeper: detailed application security requirements by level, used for working through details.

Which tools cover the OWASP Top 10 risks?

SAST finds injections and code errors, SCA finds vulnerable dependencies, IaC and container scanning finds configuration errors, DAST finds problems in a running application. Architecture and logic risks are covered by threat modeling and pentest.