Repository navigation
Matching and Statuses
Each CVE record lists the vendor, product and version ranges it affects. cvescope matches your items against those names (and the CPEs CISA's Vulnrichment adds), then checks your version against the ranges.
| Status | Meaning |
|---|---|
| affected | Your version is inside an affected range. |
| check | The product matches but the record can't settle your version, or it's an appliance or distro package whose fixes may be backported and no tracker answered. Look it up with the vendor. |
| not_affected | Your version is outside every affected range. Kept for the record, counted as "ruled out" on the page. |
| keyword | An old CVE whose record names no product mentions your item in its text. Low confidence, hidden unless you ask (report --keyword, or the checkbox on the page). |
Distros backport fixes without changing the upstream version, so openssh 1:9.6p1-3ubuntu13.5
can be patched against a CVE whose upstream range says 9.6p1 is affected. For Debian and Ubuntu,
cvescope asks the distro's own data instead:
- Debian: the Debian security tracker (via its OSV export).
- Ubuntu: Canonical's per-release package OVAL.
Both say, per source package and release, which build fixed each CVE. cvescope compares that with the installed build using dpkg's own version ordering. A few rules:
- The fix is older than or equal to your build → not_affected.
- The fix is newer than your build → affected. The reason notes Ubuntu Pro/ESM when the fix ships only there.
- The distro lists it with no fix yet → affected.
- Debian rates it "unimportant" (not patched by design) → not_affected.
- The tracker doesn't list it for that package at all → not_affected, unless the CVE is under two weeks old and may not have been triaged yet.
This applies to dpkg items with os-release, osquery deb_packages, and Debian/Ubuntu VMs found
through Proxmox. Only the releases your inventory runs are downloaded.
Some records name your product but give no usable versions. If you turn on the optional NVD lookup (Data Sources), cvescope uses NVD's CPE ranges for those before guessing from the description. Your version inside a range → affected (still check for a backported build), outside every range → not_affected, and the reason says the answer came from NVD.
CVE records spell versions every which way. cvescope handles:
- ranges with
lessThan/lessThanOrEqual, including wildcards like6.1.*; - free text: "before 2.4.60", "1.0 - 1.5", "2.1 and earlier", "Linux Kernel <= 3.1";
- OpenSSL's "Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f)";
- product-prefixed versions like
openssl-1.1.0a; - FreeBSD patch levels (
14.3-RELEASEbeforep7); - CISA's ADP data, which splits one product into many single-range entries (they're merged before evaluation);
- CNAs that set
defaultStatus: affectednext to a single "below the fix" range (read as "older than the fix", not "every other version").
Apps that update themselves (Chrome, Edge, Firefox, Thunderbird, VS Code, Signal, Telegram, Bitwarden) get one more rule: a record with no version data that's more than a year old counts as not_affected, since any build that's still updating is long past it.
When a record has no version data at all, cvescope reads the description. If every version named next to the product is older than yours ("OpenSSL 1.0.1 before 1.0.1g"), the CVE is ruled out. Open-ended wording ("and later", "since") stays check.
Match quality depends mostly on aliases: how CVE records spell your product. An alias is
vendor:product, normalized (lowercase, punctuation becomes spaces):
apache software foundation:apache http server-
*:redismatches any vendor; -
ubiquiti:unifi network*is a prefix match.
The built-in aliases live in
cvescope/collectors/packages.py.
Add your own per item:
[[inventory]]
type = "static"
name = "Gitea"
version = "1.21.4"
aliases = ["gitea:gitea"]cvescope show CVE-YYYY-NNNNN prints the record's affected entries next to the matches, which
is the quickest way to see why something did or didn't line up. If an alias is wrong or missing,
open a wrong-match issue.