What is VEX? How to say 'this vulnerability does not affect us'
By SBOMBox SBOM experts · · Updated · 3 min readShort answer: VEX, short for Vulnerability Exploitability eXchange, is a machine-readable statement that says whether a known vulnerability actually affects your product. It travels alongside your SBOM, so customers and auditors can see which scanner findings matter and why the rest do not.
Why VEX exists
Run any scanner over an SBOM and you get a long list of CVEs. Many of them cannot be exploited in your product: the vulnerable function is never called, the component is only used in tests, or a configuration blocks the attack. Without VEX, every customer who scans your SBOM asks you about every one of them. With VEX, you answer once, in a format their tools read automatically.
The four VEX statuses
| Status | Meaning | What you must add |
|---|---|---|
| not_affected | The product is not exploitable through this vulnerability | A justification |
| affected | The product is exploitable | An action statement: what users should do |
| fixed | A version of the product contains the fix | The fixed version |
| under_investigation | You are still assessing | Nothing yet; update it when you know |
Justifications for 'not affected'
A 'not affected' claim is only useful if it says why. CISA's VEX guidance defines five standard justifications:
- component_not_present: the component is not in the product.
- vulnerable_code_not_present: the component is there, but not the vulnerable code.
- vulnerable_code_not_in_execute_path: the vulnerable code is present but never runs.
- vulnerable_code_cannot_be_controlled_by_adversary: an attacker cannot reach or influence it.
- inline_mitigations_already_exist: other controls in the product prevent exploitation.
VEX formats
| Format | Maintained by | Best for |
|---|---|---|
| OpenVEX | OpenSSF | Small, standalone VEX documents; simplest to start |
| CycloneDX VEX | OWASP / Ecma | Keeping VEX in the same format as a CycloneDX SBOM |
| CSAF VEX profile | OASIS | Formal security advisories, common with large vendors |
How VEX relates to full security advisories is covered in CSAF, VEX and security advisories.
A VEX example
{
"@context": "https://openvex.dev/ns/v0.2.0",
"@id": "https://example.com/vex/2026-11-17",
"author": "Example Ltd security team",
"timestamp": "2026-11-17T09:00:00Z",
"version": 1,
"statements": [
{
"vulnerability": { "name": "CVE-2021-44228" },
"products": [{ "@id": "pkg:oci/example-api@sha256:..." }],
"status": "not_affected",
"justification": "vulnerable_code_not_in_execute_path",
"impact_statement": "JNDI lookups are disabled in our logging configuration."
}
]
}You can build a valid OpenVEX or CycloneDX VEX file without writing JSON in the free VEX generator.
VEX and the Cyber Resilience Act
The CRA requires you to identify, document and address vulnerabilities in your products. A VEX record per finding is the clearest evidence that you assessed each one, when, and on what grounds. Decide which findings to assess first with CISA KEV and EPSS. In SBOMBox, VEX decisions are stored with the project and suppress the matching finding, so your vulnerability list shows only what still needs work.
Frequently asked questions
What does VEX stand for?
Vulnerability Exploitability eXchange. It is a statement of whether a known vulnerability affects a specific product.
Is VEX part of the SBOM?
It can be. CycloneDX can carry VEX in the same document as the SBOM or in a separate file. OpenVEX and CSAF are separate documents that reference the product.
What is the difference between VEX and CSAF?
VEX is the concept and a set of statuses. CSAF is an OASIS advisory format that has a VEX profile, among others.
Who should publish VEX?
The supplier of the product, because only the supplier knows whether the vulnerable code is used. Buyers can also record their own VEX decisions internally.