← All tools
Free Tool

SBOM Checker and Component CVE Lookup

The SBOM checker matches software components against known CVEs. Paste a component list as purl, CPE, npm, pip or Maven lines, and the tool checks each component against OSV.dev and CVE records and lists the known vulnerabilities by severity. The check needs no account and stores nothing.

Last updated 8 November 2026

Key takeaways

  1. CRA Annex I Part II(1) requires an SBOM in a commonly used, machine-readable format, covering at the very least the top-level dependencies of the product.
  2. SPDX (ISO/IEC 5962) and CycloneDX represent the two primary machine-readable SBOM formats accepted across EU compliance frameworks.
  3. CycloneDX provides native support for vulnerability exploitability exchange data while SPDX offers comprehensive support for open-source license information.
  4. Mapping software components to standard Common Platform Enumeration identifiers enables automated vulnerability matching against the NVD CVE Database.
  5. An SBOM CVE check narrows which components need attention and does not on its own establish conformity with Annex I.

One component per line, as a purl, CPE, npm, Go, pip or Maven line. A plain name@version is read as npm.

The check sends the list to our server and stores nothing. Search links stay in your browser.

Frequently asked

What is an SBOM vulnerability scanner and why does it matter for CRA?+

A Software Bill of Materials (SBOM) vulnerability scanner inventories all components in a product. It covers open-source libraries, transitive dependencies, third-party SDKs, and firmware modules. It matches these components against known vulnerability feeds. CRA Annex I requires manufacturers to identify and document software components. Using dedicated SBOM tooling and regular vulnerability scans makes it fast to assess exposure whenever new CVEs are published.

Are these SBOM tools free to use?+

Yes. This SBOM component checker is part of CVD Portal's suite of free SBOM tools, with no registration or credit card required. The vulnerability check sends the component list to our server, which scans it and stores nothing. The Search links only option keeps the list in your browser. You can paste component lists from npm, pip, Maven, Go modules, or Docker image manifests for rapid triage.

What formats does this free SBOM checker support?+

This tool accepts free-form component lists generated by popular SBOM generation tools: package@version (npm, pip, Go modules), groupId:artifactId:version (Maven), and plain component names. For full SBOM document validation, use SPDX or CycloneDX format validators. This tool is designed for rapid manual triage, not full SBOM ingestion.

What SBOM formats should we use for CRA compliance?+

The two dominant SBOM formats are SPDX (ISO/IEC 5962) and CycloneDX. Both are accepted by most tooling and procurement frameworks. CycloneDX is often preferred for security use cases as it natively supports vulnerability data (VEX). SPDX is more widely supported for license compliance and open source license information. Consider generating both.

Does this tool query vulnerability databases in real time?+

Yes. The vulnerability check queries OSV.dev for each line that names its ecosystem, such as a purl, npm, pip or Maven line. A CPE line is checked against CVE records. A plain name with no ecosystem cannot be matched by version, so the checker marks it as not scanned and keeps an NVD and an OSV search link for it.

How do we map components to CPE identifiers for vulnerability management?+

CPE (Common Platform Enumeration) is the standard identifier format used by the NVD. A CPE looks like: cpe:2.3:a:vendor:product:version:*:*:*:*:*:*:*. Many package managers have CPE dictionaries. The NVD also provides a CPE search tool. Mapping your SBOM file to CPEs enables precise automated vulnerability matching across your software supply chain.

Does the SBOM checker work with a Yocto Project build?+

The Yocto Project ships a cve-check class that reports CVEs against recipe versions during a build. Yocto can also emit an SPDX document for the built image. Pasting a component list into this tool provides the faster route for a one-off triage. The native Yocto output provides the better route for a build that runs repeatedly.

How do we handle Linux kernel CVEs in an SBOM?+

A kernel entry in an SBOM names one version. A plain version match returns a large list of CVEs. Most kernel CVEs affect a subsystem that the product never enables. The applicable question is which kernel configuration ships on the device. A VEX document is where a manufacturer records that a listed CVE does not apply.

What is the difference between an SBOM checker and an SBOM validator?+

An SBOM checker asks which components carry known CVEs. An SBOM validator asks whether an SBOM document is well formed against SPDX or CycloneDX specifications.

Does an SBOM CVE check prove CRA compliance?+

No, an SBOM CVE check does not prove CRA compliance on its own. The check helps you identify vulnerable components that require remediation. requires a software bill of materials in a commonly used machine-readable format covering at least the top-level dependencies. The vulnerability handling duties in Annex I Part II apply from 11 December 2027. Conformity also needs the technical documentation, and a default-class product reaches it through self-assessment under Module A.

How does SBOM and CVE matching work?+

Matching runs in three steps named extraction, matching and verification. An SBOM security checker performs those three steps in order. During extraction, the tool reads a component list and takes the name, version and ecosystem from each line. During matching, it asks OSV.dev for advisories that affect that package at that version, or CVE records for a CPE. During verification, you check each returned CVE against the configuration the product ships. A component can be present while the affected code path is unreachable. A VEX document is where a manufacturer records that a listed CVE does not apply.

What free SBOM tools does CVD Portal provide?+

CVD Portal provides three free tools for SBOM workflows. This checker matches components against known CVEs. The SBOM validator checks whether an SBOM document is well formed. The SBOM exposure snapshot reports which products a component reaches. All three tools run without an account.

Other free CRA tools

SBOM Validator (BSI TR-03183-2 and CISA 2026 Minimum Elements)Upload or paste a CycloneDX or SPDX JSON SBOM and check it against BSI TR-03183-2 v2.1.0, the German federal guideline that concretises the CRA SBOM requirement. The validator verifies the minimum specification version of CycloneDX 1.6 or SPDX 3.0.1. It checks every required data field for the SBOM and for each component, including creator, timestamp, dependencies, licences, and hashes. Validation runs entirely in your browser. The same document is also assessed against the 2026 Minimum Elements for a Software Bill of Materials, version 2.1. CISA published this specification with seventeen partner agencies, including seven EU national cybersecurity authorities. That document replaced the 2021 NTIA minimum elements and expanded the field count from seven to seventeen. It is not EU law and creates no CRA obligation, but it is increasingly what procurement asks for. The two verdicts are reported separately and never blended because the frameworks disagree on key requirements. TR-03183-2 sets minimum format versions that the 2026 elements do not. In addition, the 2026 elements require transitive dependency coverage that CRA Annex I Part II(1) does not.SBOM Exposure SnapshotUpload or paste a CycloneDX, SPDX JSON document or dependency manifest to scan all declared components against the OSV.dev open vulnerability database. The scanner identifies known CVEs and security advisories with precise version matching, returning an immediate severity breakdown across Critical, High, Medium, and Low vulnerabilities alongside top exposed components. The live interactive scanner is available at /sbom-exposure with no registration required. The tool operates in-request and does not store your SBOM data on our servers. For continuous vulnerability monitoring and full CRA Annex I Part II(1) due diligence, CVD Portal integrates SBOM ingestion with automated alerting and CSAF 2.0 advisory generation.CVSS CalculatorCalculate CVSS 3.1 base scores for vulnerability severity assessment. Includes guidance on whether the score triggers Article 14 notification obligations under the EU Cyber Resilience Act.CSAF 2.0 Advisory ValidatorPaste your CSAF 2.0 JSON advisory and instantly validate the structure against the OASIS CSAF 2.0 schema. Identifies missing mandatory fields, invalid values, and flags common issues that would cause rejection by automated consumers and ENISA tooling.CVD Policy GeneratorBuild a complete, publication-ready CVD policy document using a guided five-step wizard. Configure your response timelines, CRA Article 13 and 14 obligations, and product scope, then export a finished Markdown policy you can publish immediately.

Keep your SBOM with your product

The 14-day trial adds the SBOM to the technical file of your product. The exposure view checks every component again each time you open it.

Start my 14-day compliance trial →Start your 14-day compliance trial →