CVE-Mapping between Trivy Analyzer and NVD #5512
Unanswered
SpiritCrusherKern
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am currently working with DependencyTrack v4.13.2 and a Trivy Analyzer Instance with the latest Version (0.67.2).
The issue is fully reproducable with the information below.
By the end of October a CVE-2025-55754 was published (https://nvd.nist.gov/vuln/detail/CVE-2025-55754) which is currently 'awaiting analysis', in particular CVSSv3.x shows Base Score 'N/A' (NVD) but also '9.6 CRITICAL' (CISA-ADP).
I scanned my container image and by 'trivy image
' I get the Severity 'LOW' by its source https://avd.aquasec.com/nvd/cve-2025-55754. This is also what I expect to get, when the Trivy Analyzer I set up with Dependency-Track analyzes component 'tomcat-embed-core v9.0.105'.
On the other hand: Mirroring CVEs from NVD gets me (shortened for more readability):
"cve": { "id": "CVE-2025-55754", "sourceIdentifier": "[email protected]", "published": "2025-10-27T18:15:42.710", "lastModified": "2025-11-04T22:16:31.360", "vulnStatus": "Awaiting Analysis", "cveTags": [], "descriptions": [...], "metrics": { "cvssMetricV31": [ { "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "type": "Secondary", "cvssData": { "version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H", "baseScore": 9.6, "baseSeverity": "CRITICAL", "attackVector": "NETWORK", "attackComplexity": "LOW", "privilegesRequired": "NONE", "userInteraction": "REQUIRED", "scope": "CHANGED", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "availabilityImpact": "HIGH" }, "exploitabilityScore": 2.8, "impactScore": 6 } ] }, ... }in particular it has Severity Critical (reproducible via curl https://services.nvd.nist.gov/rest/json/cves/2.0?cveid=CVE-2025-55754).
If both is available (i.e. the above CVE is mirrored to Dependency-Track and Trivy Analyzer is working properly), then the severity 'critical' takes precedence over 'low'.
On the other hand: If only the knowledge of trivy analyzer is available (i.e. severity 'low'), then this knowledge is stored into the vulnerability database of Dependency-Track.
Why is that? How does the Mapping between Trivy Findings and NVD work within Dependency-Track? What is the correct way to read this (although I think the answer depends on policies).
Beta Was this translation helpful? Give feedback.
All reactions