Skip to content

VEX and suppression

The VEX formats the Vulnesis CLI reads and writes, where VEX changes scan results, and how ignore rules, nosec comments and VEX suppress findings.

Updated 04 Nov 2026Markdown

VEX is for teams that publish software and must tell its users which reported vulnerabilities do not affect it, and for teams that receive those statements and want their scans to stop reporting what a vendor has already ruled out. An SBOM lists what is in a product. VEX says which of the vulnerabilities in it matter, and attestation proves who signed either one. Use VEX when the question is whether a finding applies, not what is installed.

A VEX statement says whether a product is affected by a vulnerability. The CLI writes VEX for its own triage decisions, reads VEX that anyone else wrote, applies it to SBOMs and scans, and sends it to Vulnesis, where false-positive and won’t-fix statements become suppression rules.

Two mechanisms hide findings, and they are reported differently:

Mechanism Who asserts it Scope Reported as
VEX statements (--vex-file, --vex, declared VexSource documents, vex apply) The document’s author, often an upstream vendor Vulnerabilities in an SBOM “VEX not affected” or “VEX fixed”
Ignore rules (vulnetix ignore) and nosec comments Your team Findings of every scanner “suppressed by ignore rules” or “by nosec comments”

Formats

Format Read Written
OpenVEX 0.2.0 yes, recognised by an @context on openvex.dev vex merge, bom enrich companion file, triage --vex-format openvex, scan reconciliation files under .vulnetix/
CycloneDX VEX yes, any document with bomFormat: CycloneDX. Only vulnerabilities[] entries with an analysis block are statements. triage (default --vex-format cdx), vex apply --out, bom enrich
CSAF 2.0 VEX yes, recognised by a document.category containing vex no

All three are normalised into one statement model, so matching and application work the same whichever format the author used. The CLI validates against the vendored openvex-0.2.0 and cyclonedx-1.7 schemas in cli/schemas/third_party/.

Status mapping

OpenVEX status CycloneDX analysis.state CSAF product status Suppresses in vex apply and scans
not_affected not_affected, false_positive known_not_affected yes
fixed resolved, resolved_with_pedigree fixed yes
affected exploitable known_affected no, adds an action statement
under_investigation in_triage under_investigation no

To state one of these CycloneDX states on a finding in an SBOM the CLI writes, set vulnerabilities[].analysis in an overlay file.

Commands

Command Does
vulnetix vex apply Apply statements to an SBOM and report total, suppressed and effective counts
vulnetix vex ls, validate, merge Review, check and combine VEX documents
--vex-file and --vex on scan, sca, sast, secrets, containers, iac Apply VEX from files, directories and https URLs before the quality gates. --vex needs CLI v4.2.0. An authenticated scan also applies the Resolve Platform’s statements (CLI v4.4.0).
vulnetix ignore (alias suppress) Add, list, remove and sync ignore rules
vulnetix vdb vex get, vdb vex list Read VEX that Vulnesis holds for a CVE. See VDB API.

To apply a vendor’s VEX document to a scan and check it step by step, follow the VEX quickstart. Every VEX file the CLI writes under .vulnetix/ is on VEX the CLI writes.

What reaches Vulnesis

When a command is authenticated, the VEX it read or wrote is sent to POST /v2/cli.vex-ingest, and the findings ignore rules and nosec comments hid are reported to cli.finalize. See VEX sent to Vulnesis.

A standing source of suppression rules, read from a TEA server, an S3 bucket, a git repository or URLs, is the VexSource kind. Since CLI v4.2.0 a scan also reads the path and urls sources declared under .vulnetix/config itself, and since CLI v4.4.0 an authenticated scan applies the statements the Resolve Platform holds for every source type, tea, s3 and git included; see Declared VexSource documents, Statements the Resolve Platform holds and VEX documents as suppression rules.

GitHub Actions

Validate, list, merge or apply VEX documents in a workflow with the vex GitHub Action.

Platform IaC

Suppression rules you write are Suppression documents. A standing source of VEX, read from a TEA server, an S3 bucket, a git repository or URLs, is a VexSource; see VEX documents as suppression rules. Rules from a local .vulnetix/memory.yaml and vulnetix ignore stay as they are. See the kind catalogue.

When Drift protection is on, a change made in the Resolve Platform or through a legacy API to a suppression rule that is managed as code (by Terraform or a repository) is refused with HTTP 409 managed_by_platform_iac. Change it where it is declared, or ask an owner to turn Drift protection off. Rules written as a side effect of triaging a finding are not blocked.

esc
↑ ↓ move↵ openSearches in your browser. A key like autonomy.max or a code like threshold_required jumps straight to it.