Repository navigation
Reason CVE is not found for component with CPE #7950
|
Hello everyone, I am currently taking a look at Dependency Track with some test projects/components. I have a zlib component with the CPE cpe:2.3:a:zlib:zlib:1.3.2:::::::* and no PURL. Based on other SCA scanners I would expect CVE-2026-85091 to be matched for this component, however it is not. Is this a limitation of the NVD entry (https://nvd.nist.gov/vuln/detail/cve-2026-85091) which oddly does not contain associated CPEs? |
Replies: 1 comment 4 replies
|
Yes, the missing NVD applicability data explains the NVD/CPE matching path here. The Dependency-Track's known-vulnerability analysis documentation The absence of a PURL also matters when comparing results from other scanners: analyzers such as OSS For this comparison, record the scanner's advisory source and Dependency-Track version/enabled analyzers. |

Yes, the missing NVD applicability data explains the NVD/CPE matching path here. The
authoritative NVD API record
currently has
vulnStatus: "Awaiting Analysis"and noconfigurationscontaining affected CPE matches.That is different from an analyzed record saying your component is unaffected.
Dependency-Track's known-vulnerability analysis documentation
says its NVD matching uses CPEs and the CPE name-matching rules. A version appearing in the CVE's prose
description does not provide the missing structured CPE applicability information. Your valid component
CPE alone cannot supply the other side of that match.
The absence of a PURL also matters when comparing results from other scanners: …