Analysis
Common Weaknesses
The most common CWE weakness classes across Erlang ecosystem CVEs
The chart below shows the most common weaknesses found in vulnerabilities across the Erlang ecosystem. Understanding which weakness types recur most often helps library authors and application developers focus their security efforts where they matter most.
Each CVE is mapped to its CWE (Common Weakness Enumeration) using the MITRE CWE hierarchy. A slice's count includes every CVE reachable anywhere below it in the hierarchy, not just CVEs assigned that exact CWE — click a slice or legend row to drill into its direct children and see the same breakdown one level down.
Excessive Code Complexity CWE-1120 CWE-1120 at MITRE
The code is too complex, as calculated using a well-defined, quantitative measure.
Modules with Circular Dependencies CWE-1047
0
(0.0%)
Invokable Control Element with Variadic Parameters CWE-1056
0
(0.0%)
Excessive Number of Inefficient Server-Side Data Accesses CWE-1060
0
(0.0%)
Invokable Control Element with Signature Containing an Excessive Number of Parameters CWE-1064
0
(0.0%)
Unconditional Control Flow Transfer outside of Switch Block CWE-1075
0
(0.0%)
Source Code File with Excessive Number of Lines of Code CWE-1080
0
(0.0%)
Loop Condition Value Update within the Loop CWE-1095
0
(0.0%)
Excessive Use of Unconditional Branching CWE-1119
0
(0.0%)
Excessive McCabe Cyclomatic Complexity CWE-1121
0
(0.0%)
Excessive Halstead Complexity CWE-1122
0
(0.0%)
Excessive Use of Self-Modifying Code CWE-1123
0
(0.0%)
Excessively Deep Nesting CWE-1124
0
(0.0%)
Excessive Attack Surface CWE-1125
0
(0.0%)