When to use vulnerabilities
- Enrich a CVE with CVSS, EPSS, exploitation, and affected-software context.
- Connect a scanner finding to advisories, weaknesses, affected software, and attack patterns.
- Prioritize remediation using several independent risk signals.
- Verify important values against the public records that supplied them.
Relationships
Relationships provide context, not proof that every connected software version is affected or that every attack pattern is feasible. Check affected targets and provenance before making an automated decision. See Security data model for relationship cardinalities.
Schema
Every vulnerability 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.