CWE-637: Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')
Also known as: Unnecessary Complexity
The product uses a more complex mechanism than necessary, which could lead to resultant weaknesses when the mechanism is not correctly understood, modeled, configured, implemented, or used.
Last updated
Overview
Security mechanisms should be as simple as possible. Complex security mechanisms may engender partial implementations and compatibility problems, with resulting mismatches in assumptions and implemented security. A corollary of this principle is that data specifications should be as simple as possible, because complex data specifications result in complex validation code. Complex tasks and systems may also need to be guarded by complex security checks, so simple systems should be preferred.
Real-world CVEs
1 recorded CVEs are caused by CWE-637 (Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')). The highest-severity and most recent are shown first. 1 new CWE-637 CVE has been recorded so far in 2026.
Common consequences
What can happen when CWE-637 is exploited.
Other
Affects: Other
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.