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.
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.