Skip to main content
Vulnerabilities describe security issues identified by a preferred public identifier, usually a CVE. Zero combines compatible claims about severity, exploitation, affected software, remediation, and related security concepts into one normalized entity. Use a vulnerability when your workflow starts with a CVE or needs a stable public anchor for triage, prioritization, remediation, or enrichment. Software remains a versionless product identity. For supported packages, registry-observed release children can be assessed against this vulnerability’s normalized affected ranges without turning each version into a separate Software record.

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.
Severity, EPSS, CISA KEV membership, and observed exploitation answer different questions. A high severity does not prove exploitation, and the absence of an exploitation signal does not prove that exploitation has not occurred.

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.

API pages