Hello, you are using an old browser that's unsafe and no longer supported. Please consider updating your browser to a newer version, or downloading a modern browser.

Global Accelerated Learning • Est. 1999
Glossary Term CWE SANS Top 25

Training Camp • Cybersecurity Glossary

What is CWE SANS Top 25?

It is the annual, data-driven ranking of the 25 most dangerous software weaknesses (e.g. CWE-79 XSS, CWE-787) — broader than the OWASP Top 10, maintained by MITRE/CISA.

Glossary > Application & API Security > CWE SANS Top 25

CWE SANS Top 25 — It is the annual, data-driven ranking of the 25 most dangerous software weaknesses (e.g

Understanding CWE SANS Top 25

The CWE/SANS Top 25 Most Dangerous Software Weaknesses is an annually published, data-driven list ranking the most common and impactful types of software weaknesses. Compiled by MITRE with CISA — historically in collaboration with the SANS Institute — it prioritizes the weaknesses that appear most frequently in real vulnerabilities and carry the highest severity, helping teams focus on the flaws that cause the most harm.

It works by analyzing real-world vulnerability data rather than expert opinion alone. MITRE scores each weakness (identified by CWE ID) using a formula combining prevalence — how many CVE records reference it across the National Vulnerability Database — and average severity from CVSS scores. The 2024 edition, for instance, analyzed roughly 31,770 CVE records, with Cross-Site Scripting (CWE-79) and Out-of-Bounds Write (CWE-787) topping the list and SQL Injection (CWE-89) close behind. The list is recalculated and reissued each year to track the shifting threat landscape.

It matters for security because it gives developers and security teams an evidence-based prioritization tool. Unlike the OWASP Top 10, which targets web application risks specifically, the CWE Top 25 spans a broader range of software — desktop, embedded, and network components — at the level of root-cause weaknesses. Organizations use it to focus code review and security testing, drive secure-coding training on the most damaging flaw classes, and set standards that address the highest-risk issues first rather than chasing theoretical concerns.

For example, a development organization adopting the CWE Top 25 might map its static analysis rules to the listed weaknesses, require training and unit tests specifically for out-of-bounds writes and injection flaws, and gate releases on scanning for those CWEs. By concentrating limited security effort on the weaknesses statistically most likely to be exploited and most damaging when they are, the team reduces its real exposure faster than by treating all potential issues equally.

Learn More About CWE SANS Top 25:

Ready to Get Certified?

Turn knowledge into credentials with our instructor-led cybersecurity boot camps.

View All Courses →