<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/sbom-cve-check-1-3-2-and-1-3-3-improved-sbom-handling-and-more-robust-cve-analysis-bootlin-3lmrykk0r" -->

---
title: sbom-cve-check 1.3.2 and 1.3.3: improved SBOM handling...
description: Bootlin's sbom-cve-check tool, used as the Yocto Project's official CVE monitoring tool, received two releases: 1.3.2 (June) improved Zstandard compression...
canonical: https://daily.dev/posts/sbom-cve-check-1-3-2-and-1-3-3-improved-sbom-handling-and-more-robust-cve-analysis-bootlin-3lmrykk0r
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: sbom-cve-check 1.3.2 and 1.3.3: improved SBOM handling and more robust CVE analysis – Bootlin | daily.dev
og:description: Bootlin's sbom-cve-check tool, used as the Yocto Project's official CVE monitoring tool, received two releases: 1.3.2 (June) improved Zstandard compression...
og:url: https://daily.dev/posts/sbom-cve-check-1-3-2-and-1-3-3-improved-sbom-handling-and-more-robust-cve-analysis-bootlin-3lmrykk0r
og:image: https://api.daily.dev/og/posts/3lmRYKk0R.png
og:image:alt: sbom-cve-check 1.3.2 and 1.3.3: improved SBOM handling and more robust CVE analysis – Bootlin
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# sbom-cve-check 1.3.2 and 1.3.3: improved SBOM handling and more robust CVE analysis – Bootlin

**[Bootlin](https://daily.dev/sources/bootlin)** · 5 min read · 0 upvotes · 0 comments

## Summary

Bootlin's sbom-cve-check tool, used as the Yocto Project's official CVE monitoring tool, received two releases: 1.3.2 (June) improved Zstandard compression support, extended simple annotation YAML keys, and fixed Linux kernel source file filtering and detection of incomplete kernel source lists. 1.3.3 (August) added handling of disputed CVEs to generate 'not affected' VEX assessments, more flexible CVE version-range matching (comparison operators, date-boundary and distro packaging suffix safeguards), fixed CVE database Git repository update issues, and added uv support plus a new contributing guide.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://bootlin.com/blog/sbom-cve-check-1-3-2-and-1-3-3-improved-sbom-handling-and-more-robust-cve-analysis>

## Questions this post answers

### What changed in sbom-cve-check 1.3.3 for handling disputed CVEs?

Sbom-cve-check 1.3.3 can generate a 'not affected' VEX assessment when a vulnerability is marked as disputed, rather than treating it as an ordinary affected/not-affected matching problem. This better reflects information from the CVE ecosystem and is particularly useful for automated vulnerability-management workflows that rely on accurate VEX assessments. Released August 3, 2026.

_daily.dev surfaces tooling updates like this for teams automating CVE and VEX vulnerability workflows._

### How does sbom-cve-check handle CVE version ranges with date boundaries or distro packaging suffixes?

Version 1.3.3 adds safeguards so that version ranges with a date boundary, such as 2024-01-01, are ignored when the component version is not itself a date, for example a semantic version. It also ignores certain version ranges with distribution-specific packaging suffixes like .el7, following documented rules, to avoid inappropriate version comparisons and incorrect vulnerability assessments.

_engineers tuning CVE matching accuracy can track these edge-case fixes on daily.dev._

### What are the requirements for sbom-cve-check to consider a Linux kernel compiled source file list complete?

As of version 1.3.2, sbom-cve-check only considers a list of compiled Linux kernel source files usable when it contains at least one of init/main.c, include/linux/module.h, or a file ending in .mod.c. This prevents incomplete kernel source information from producing misleading vulnerability assessments, alongside filtering of Makefile, Kconfig, and internal/built-in path entries.

_teams securing embedded Linux builds can follow SBOM analysis fixes like this via daily.dev._

## Similar posts on daily.dev

- [sbom-cve-check updates: integrated in Yocto 6.0 Wrynose, Schneider Electric support, new releases, and more – Bootlin](https://daily.dev/posts/sbom-cve-check-updates-integrated-in-yocto-6-0-wrynose-schneider-electric-support-new-releases-a-vdyr1d99s) · Bootlin · 0 upvotes · 0 comments
- [SPDX SBOM Generation Tool Proposed For The Linux Kernel](https://daily.dev/posts/spdx-sbom-generation-tool-proposed-for-the-linux-kernel-behz0husd) · Phoronix · 0 upvotes · 0 comments
- [Rethinking Post-Deployment Vulnerability Detection](https://daily.dev/posts/rethinking-post-deployment-vulnerability-detection-u1tfs0ejg) · OpenSSF · 0 upvotes · 0 comments
- [SBOM Generation for Container Workflows](https://daily.dev/posts/sbom-generation-for-container-workflows-nctydjhq9) · Docker · 4 upvotes · 0 comments
- [How SBOMs and Engineering Discipline Can Help You Avoid Trivy’s Compromise](https://daily.dev/posts/how-sboms-and-engineering-discipline-can-help-you-avoid-trivy-s-compromise-c6zqbaibq) · InfoQ · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#sbom](https://daily.dev/tags/sbom)

[View this post on daily.dev](https://daily.dev/posts/sbom-cve-check-1-3-2-and-1-3-3-improved-sbom-handling-and-more-robust-cve-analysis-bootlin-3lmrykk0r)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"sbom-cve-check 1.3.2 and 1.3.3: improved SBOM handling and more robust CVE analysis – Bootlin","url":"https://daily.dev/posts/sbom-cve-check-1-3-2-and-1-3-3-improved-sbom-handling-and-more-robust-cve-analysis-bootlin-3lmrykk0r","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/sbom-cve-check-1-3-2-and-1-3-3-improved-sbom-handling-and-more-robust-cve-analysis-bootlin-3lmrykk0r"},"datePublished":"2026-08-26T09:38:35.258Z","dateModified":"2026-09-13T18:57:27.683Z","description":"Bootlin's sbom-cve-check tool, used as the Yocto Project's official CVE monitoring tool, received two releases: 1.3.2 (June) improved Zstandard compression...","image":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","thumbnailUrl":"https://media.daily.dev/image/upload/s--58gMhC4P--/f_auto/v1722860399/public/Placeholder%2012","isAccessibleForFree":true,"articleSection":"Bootlin","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Bootlin","logo":"https://media.daily.dev/image/upload/s---n2KdAAq--/f_auto,q_auto/v1780213510/logos/bootlin?_a=BAMAMiWQ0","url":"https://daily.dev/sources/bootlin"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/sbom-cve-check-1-3-2-and-1-3-3-improved-sbom-handling-and-more-robust-cve-analysis-bootlin-3lmrykk0r","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,sbom","timeRequired":"PT5M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Bootlin","item":"https://daily.dev/sources/bootlin"},{"@type":"ListItem","position":3,"name":"sbom-cve-check 1.3.2 and 1.3.3: improved SBOM handling and more robust CVE analysis – Bootlin"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/sbom-cve-check-1-3-2-and-1-3-3-improved-sbom-handling-and-more-robust-cve-analysis-bootlin-3lmrykk0r#faq","mainEntity":[{"@type":"Question","name":"What changed in sbom-cve-check 1.3.3 for handling disputed CVEs?","acceptedAnswer":{"@type":"Answer","text":"Sbom-cve-check 1.3.3 can generate a 'not affected' VEX assessment when a vulnerability is marked as disputed, rather than treating it as an ordinary affected/not-affected matching problem. This better reflects information from the CVE ecosystem and is particularly useful for automated vulnerability-management workflows that rely on accurate VEX assessments. Released August 3, 2026. daily.dev surfaces tooling updates like this for teams automating CVE and VEX vulnerability workflows."}},{"@type":"Question","name":"How does sbom-cve-check handle CVE version ranges with date boundaries or distro packaging suffixes?","acceptedAnswer":{"@type":"Answer","text":"Version 1.3.3 adds safeguards so that version ranges with a date boundary, such as 2024-01-01, are ignored when the component version is not itself a date, for example a semantic version. It also ignores certain version ranges with distribution-specific packaging suffixes like .el7, following documented rules, to avoid inappropriate version comparisons and incorrect vulnerability assessments. engineers tuning CVE matching accuracy can track these edge-case fixes on daily.dev."}},{"@type":"Question","name":"What are the requirements for sbom-cve-check to consider a Linux kernel compiled source file list complete?","acceptedAnswer":{"@type":"Answer","text":"As of version 1.3.2, sbom-cve-check only considers a list of compiled Linux kernel source files usable when it contains at least one of init/main.c, include/linux/module.h, or a file ending in .mod.c. This prevents incomplete kernel source information from producing misleading vulnerability assessments, alongside filtering of Makefile, Kconfig, and internal/built-in path entries. teams securing embedded Linux builds can follow SBOM analysis fixes like this via daily.dev."}}]}
```

