← Back to Compliance
Compliance Framework

CWE Top 25: the most dangerous software weaknesses.

The CWE Top 25 Most Dangerous Software Weaknesses identifies the software defects most frequently exploited to compromise systems. MergeGuide ships detection rules mapped to these weaknesses and enforces them across the languages your team writes in, from the first line of code.

The catalog

CWE and the vulnerability catalog

The Common Weakness Enumeration (CWE) is a community-developed list of software and hardware weakness types, maintained by MITRE. The CWE Top 25 is compiled annually from CVE data, representing the weaknesses that produce the most real-world exploits across all software categories.

Unlike OWASP, which focuses on web applications, CWE Top 25 covers weaknesses across all software types including systems software, embedded systems, and enterprise applications. It is referenced by NIST NVD, CISA KEV, and used by security researchers globally as the canonical weakness taxonomy.

MergeGuide's Free tier includes CWE Top 25 detection, bundled with OWASP Top 10 coverage in the baseline tier. 106 Semgrep rules and 237 regex patterns map to the CWE Top 25 across the supported languages, with no subscription required.

Mapped weaknesses

Top CWE categories covered

MergeGuide detection rules map to the highest-ranked weaknesses in the catalog:

  • CWE-787, Out-of-bounds Write: detecting unsafe memory operations
  • CWE-79, Cross-site Scripting: detecting unsanitized output rendering
  • CWE-89, SQL Injection: detecting unparameterized database queries
  • CWE-416, Use After Free: detecting unsafe memory management patterns
  • CWE-78, OS Command Injection: detecting unsanitized shell execution
  • CWE-20, Improper Input Validation: detecting missing validation on inputs
  • CWE-125, Out-of-bounds Read: detecting unsafe buffer access patterns
  • CWE-22, Path Traversal: detecting user-controlled file path operations
  • CWE-352, Cross-Site Request Forgery: detecting missing CSRF protections
  • CWE-434, Unrestricted File Upload: detecting unsafe file handling
Detection engine

CWE Top 25 detection patterns

Selected examples of what MergeGuide catches. These patterns run on every commit, across the languages your team writes in.

CWE ID What MergeGuide Detects Severity
CWE-89: SQL InjectionUnparameterized database queries concatenating user-controlled inputCritical
CWE-79: XSSUser-controlled data rendered in HTML output without encodingCritical
CWE-78: OS Command InjectionShell execution calls with unsanitized arguments from user inputCritical
CWE-798: Hardcoded CredentialsPasswords, API keys, and secrets embedded in source codeCritical
CWE-22: Path TraversalFile system operations with user-controlled path componentsHigh
CWE-352: CSRFState-changing endpoints missing CSRF token validationHigh
CWE-434: Unrestricted UploadFile upload handlers without type or size validationHigh
Coverage

Why CWE Top 25 lives in MergeGuide

FREE

Free tier baseline

CWE Top 25 detection is included in MergeGuide's Free tier alongside OWASP Top 10. Every developer gets detection coverage for the most exploited software weaknesses with no subscription required, because baseline security should not be a paid feature.

CVE

CVE and KEV alignment

CWE Top 25 is compiled from CVE data and aligns directly with CISA's Known Exploited Vulnerabilities catalog. MergeGuide's detection rules target the code patterns that produce these weaknesses, catching the bugs that become CVEs before they ship.

LANG

Cross-language coverage

CWE Top 25 weaknesses appear across programming languages. MergeGuide's detection rules span Go, Python, JavaScript, TypeScript, Java, C#, Ruby, PHP, C/C++, Terraform, and Dockerfile, so the same weakness is caught wherever your team writes it.

Eliminate the most exploited weaknesses from your codebase.

Start free. CWE Top 25 and OWASP Top 10 detection included, no credit card required.

Get Started Free Book a Demo