SBOM Vulnerability Scanner
Find known vulnerabilities in the components of a CycloneDX or SPDX SBOM.
How it works
- Load an SBOMDrop a CycloneDX or SPDX file, paste it, or try the sample. The file is read in your browser.
- Review what is sentOnly package URLs go to the open OSV database, straight from your browser. You see the count before anything is sent.
- Triage the resultsSort by severity, see which versions fix each advisory, export CSV, or write VEX statements for the ones that do not affect you.
New vulnerabilities appear every day. Get told when one hits a release.
SBOMBox re-checks every stored SBOM nightly against OSV, GitHub advisories, NVD and the CISA KEV catalogue, alerts you when something new affects a shipped release, and keeps your VEX decisions with it.
Frequently asked questions
Where does the vulnerability data come from?
From OSV.dev, the open vulnerability database run by Google that combines GitHub Security Advisories, PyPA, RustSec, the Go database and others. The free scan does not check the CISA KEV catalogue; the SBOMBox platform does.
What is sent over the network?
Only package URLs (ecosystem, name and version) go to the OSV API, straight from your browser. The SBOM file and your product name are never sent. SBOMBox receives nothing.
Why are some components not scanned?
OSV matches by package URL. Components without a purl, or with a type OSV does not cover such as generic or OS packages without a distro qualifier, are listed as not scanned.
How do I keep watching for new vulnerabilities?
This is a one-time scan. SBOMBox re-checks every stored SBOM nightly against OSV, GHSA, NVD and CISA KEV and alerts you when something new affects a release.