VEX Generator
Write a VEX statement that tells customers whether a vulnerability actually affects your product.
Components from an SBOM (optional)
- Add the product name.
- Add an author. OpenVEX requires one, and customers need to know who made the statement.
Statements
One statement per vulnerability. Name the affected components, or leave them empty to cover the whole product.
- Add the product name.
- Add an author. OpenVEX requires one, and customers need to know who made the statement.
- Statement 1: Add the vulnerability ID.
How it works
- Describe the productName the product and version, and who makes the statement. Optionally load its SBOM to pick components by name.
- Add a statement per vulnerabilitySet the status. Not affected needs a justification, affected needs an action for users. Problems are flagged as you type.
- Copy or downloadGet a valid OpenVEX 0.2.0 or CycloneDX 1.6 VEX document. Publish it next to your SBOM or send it to the customer who asked.
Keep VEX decisions with the release they belong to.
SBOMBox stores VEX statements per release, applies them to nightly OSV, GitHub, NVD and CISA KEV matches so suppressed findings stay suppressed, and exports the evidence for customers and CRA technical files.
Frequently asked questions
What is VEX?
Vulnerability Exploitability eXchange: a machine-readable statement that a known vulnerability does or does not affect a product, and why. It stops scanners and customers from chasing CVEs that cannot be reached.
OpenVEX or CycloneDX VEX?
OpenVEX is a small standalone format, used by Sigstore and many scanners. CycloneDX VEX fits teams that already ship CycloneDX SBOMs. Both carry the same four statuses and justifications.
What justification should I use for not_affected?
Pick the one that is true and provable: the component is not present, the vulnerable code is not present, it is not in the execute path, it cannot be controlled by an adversary, or inline mitigations already exist.
Does the CRA require VEX?
The CRA requires you to handle and document vulnerabilities, and to tell users about fixes. VEX is the most common machine-readable way to do that, and BSI TR-03183-2 references it directly.