> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zdlake.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Vulnerabilities

> Understand CVE-centered records, risk signals, affected software, and supporting evidence.

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

| Related concept | What the relationship explains |
| - | - |
| [Advisory](https://docs.zdlake.com/concepts/advisories.md) | Which publishers describe the vulnerability and what they recommend. |
| [Weakness](https://docs.zdlake.com/concepts/weaknesses.md) | The class of software flaw associated with the vulnerability. |
| [Software](https://docs.zdlake.com/concepts/software.md) | The products connected through affected assertions and their version scope. |
| [Attack pattern](https://docs.zdlake.com/concepts/attack-patterns.md) | Attacker behavior relevant to exploiting the underlying weakness. |

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](https://docs.zdlake.com/concepts/security-data-model.md) for relationship cardinalities.

## Schema

Every vulnerability detail response starts with these fields:

| Field | Meaning |
| - | - |
| `entity` | Always `vulnerability`. |
| `entity_id` | Durable Zero identifier for the entity. |
| `id` | Preferred public identifier, such as `CVE-2021-44228`. |
| `aliases` | Other public identifiers associated with the same issue. |
| `title` | Human-readable title. |
| `summary` | Normalized description assembled from available claims. |
| `state` | Current lifecycle state of the entity. |
| `published_at` | Upstream publication time when available. |
| `source_updated_at` | Most recent relevant upstream update time. |
| `updated_at` | Time Zero last updated the entity. |
| `revision_id` | Identifier for the normalized revision returned by the request. |

Request optional projections when you need more detail:

| Projection | Contents |
| - | - |
| `overview` | Preferred severity, EPSS, exploitation, remediation summary, and related weaknesses. |
| `risk` | Preferred CVSS, source CVSS assessments, EPSS, and exploitation evidence. |
| `remediation` | Remediation state, recommended action, fixed versions, and references. |
| `affected_targets` | Software identities, affected ranges, fixed versions, and supporting product coordinates. |
| `software_releases` | Up to 100 current registry-observed releases connected to the vulnerability, ordered by ecosystem-correct version semantics. The nested assessment is filtered to this vulnerability and includes source aggregation, conflict state, and explicit truncation metadata. |
| `relationships` | Related entities grouped by type, including direction and supporting sources. |
| `provenance` | Field-level evidence keyed by JSON Pointer path. |

Search responses are intentionally more compact than detail responses. Use the API pages for the complete request and response schemas.

## API pages

| Page | Use it for |
| - | - |
| [Search vulnerabilities](https://docs.zdlake.com/vulnerabilities/search.md) | Search and filter vulnerability records. |
| [Get a vulnerability](https://docs.zdlake.com/vulnerabilities/get.md) | Retrieve one vulnerability and request optional projections. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.