<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>cve on toorun.dev</title><link>https://toorun.dev/tags/cve/</link><description>Recent content in cve on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 20 Sep 2026 10:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/cve/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Check CVEs and Vulnerabilities in a Yocto Image</title><link>https://toorun.dev/posts/yocto-cve-vulnerability-check-package-inventory/</link><pubDate>Sun, 20 Sep 2026 10:00:00 +0000</pubDate><guid>https://toorun.dev/posts/yocto-cve-vulnerability-check-package-inventory/</guid><description>How to Check CVEs and Vulnerabilities in a Yocto Image Yocto can check known CVEs for the recipes used to build an image. The useful workflow is:
Enable the Yocto CVE checker. Build the image and read the generated report. Record the package version, CVE, status, and fix. Verify the final device image separately. 1) Enable CVE checking Add this to build/conf/local.conf:
INHERIT += &amp;#34;cve-check&amp;#34; # Optional: fail the build when an unresolved CVE is found.</description></item></channel></rss>