Definition
What is VEX?
VEX (Vulnerability Exploitability eXchange) · also: Vulnerability Exploitability eXchange, VEX document
Short answer
VEX, or Vulnerability Exploitability eXchange, is a machine-readable statement of whether a known vulnerability affects a specific product and why.
VEX adds product-specific exploitability context to vulnerability findings associated with an SBOM. Common statuses are affected, not affected, fixed and under investigation; formats encode these statuses according to their own models. CycloneDX VEX, for example, records an analysis state such as not_affected, exploitable, in_triage or resolved. A statement can include a justification, action and supporting detail, allowing downstream teams to understand a manufacturer's decision instead of treating every component match as an exploitable product vulnerability. Vellaci records per-product and per-version triage with reasons and exports CycloneDX 1.5 VEX documents.
A VEX document answers the question an SBOM cannot: a vulnerable component is present, but is the product affected? It is produced by the party that knows the product — normally the manufacturer — and is versioned, because the answer changes when code, configuration or the advisory changes. VEX exists in several encodings: CycloneDX (inside or alongside the BOM), the VEX profile of OASIS CSAF 2.0, OpenVEX and the security profile of SPDX 3.0.
| Status | Meaning | What the statement must add |
|---|---|---|
| not_affected | The product is not affected by the vulnerability | A justification (for example component_not_present, vulnerable_code_not_present, vulnerable_code_not_in_execute_path, vulnerable_code_cannot_be_controlled_by_adversary, inline_mitigations_already_exist) or an impact statement |
| affected | The product is affected | An action statement: what users should do, such as update or apply a mitigation |
| fixed | The listed product versions contain a fix | — |
| under_investigation | Not yet known whether the product is affected | — |
Reference: CISA minimum requirements for VEX; CycloneDX VEX specification
Updated · Paraphrase for orientation, not legal advice.
Frequently asked questions
- What is a VEX document?
- A machine-readable file, usually published by a manufacturer, that states for one or more products and versions whether each listed vulnerability affects them — not affected, affected, fixed or under investigation — with a justification or recommended action.
- What is the difference between an SBOM and VEX?
- An SBOM lists what a product contains; VEX states whether known vulnerabilities in those components actually affect the product. SBOM matching produces candidate vulnerabilities; VEX records the decision about each one.
- Does the CRA require VEX?
- The CRA does not name VEX. It requires manufacturers to identify, document and address vulnerabilities and to disclose fixed ones; a VEX record per product version is a practical, machine-readable way to evidence those decisions and share them with customers.
- Which VEX format should I use?
- Use the format your consumers read. CycloneDX VEX fits teams already producing CycloneDX SBOMs; the CSAF VEX profile fits organisations publishing security advisories in CSAF; OpenVEX is a minimal standalone format.