OWASP A04 Highlights Cryptographic Failures Driven by Application Code Bugs
Regulatory & Policy · 2 sources · Updated 4mo ago · First seen Jul 30, 2026

OWASP’s Top 10 2025 category A04: Cryptographic Failures emphasizes that many security weaknesses tied to cryptography stem from implementation mistakes rather than broken cryptographic primitives. Supporting analysis from Semgrep says the most common patterns in GitHub Security Advisories mapped to A04:2025 involve improper signature verification (CWE-347) and use of risky or obsolete algorithms (CWE-327), with failures often occurring in the validation logic surrounding attacker-controlled inputs.
One cited example, CVE-2021-43572, showed how an implementation could accept an invalid ECDSA signature with r=0 and s=0 because the code did not enforce required value ranges, allowing signature verification to be bypassed. The reporting underscores that organizations should treat cryptographic risk as a software assurance problem as much as a mathematics problem, prioritizing code review and testing for input validation, signature checks, and algorithm selection in applications that rely on encryption or digital signatures.


