Skip to main content
Weaknesses represent normalized Common Weakness Enumeration (CWE) records. A weakness describes a class of software or design flaw that can produce many different vulnerabilities. Use weaknesses to move from individual CVEs toward root-cause analysis, secure development guidance, taxonomy reporting, and recurring risk patterns.

When to use weaknesses

  • Group vulnerabilities by their underlying flaw instead of affected product.
  • Explain recurring engineering risks using a shared taxonomy.
  • Connect prevention and detection guidance to concrete vulnerabilities.
  • Organize AppSec reporting, education, and control coverage around CWE classes.
A CWE relationship is explanatory, not a complete exploit narrative. Use related vulnerabilities for concrete affected software and related attack patterns for adversary behavior.

Relationships

Deprecated or remapped CWEs can remain useful historical identifiers. Check state, relationships, and provenance before using them as durable reporting groups. See Security data model for relationship cardinalities.

Schema

Every weakness detail response starts with these fields: Request optional projections when you need more detail: Search responses are intentionally more compact than detail responses. Use the API pages for the complete request and response schemas.

API pages