What is an SBOM, and what is VEX?
Updated 2026-11-17
Short answer
An SBOM (software bill of materials) is a machine-readable list of every component inside a piece of software, with its version and licence. VEX (Vulnerability Exploitability eXchange) is a companion document that says, for each known vulnerability in those components, whether your product is actually affected.
SBOM formats
There are two widely used formats: CycloneDX and SPDX. Both are open standards and most tools read both. scancontainer exports either one for any image you scan.
What VEX adds
An SBOM alone produces alarm: every component with a known CVE looks like a problem. VEX gives each one a status.
- Not affected: the vulnerable code is absent or cannot be reached.
- Affected: it applies and needs action.
- Fixed: the version in the product already has the patch.
- Under investigation: not decided yet.
Common VEX formats are OpenVEX, CycloneDX VEX and CSAF.
Who asks for an SBOM
- The EU Cyber Resilience Act, Regulation (EU) 2024/2847, requires makers of products with digital elements to draw up an SBOM as part of vulnerability handling.
- US Executive Order 14028 made SBOMs an expectation for software sold to federal agencies.
- Customers in regulated sectors increasingly ask for one in procurement.
How to get an SBOM for a container image
Scan the image and export the result. A good SBOM also includes what does not come from a package manager, such as binaries copied by hand, because those are the components other tools miss.