Triage a new scanner finding
Record a finding as an entry in your Vulnlog file as soon as a scanner reports it, then add your verdict to the entry when you’ve analysed it. Your reports and suppression files pick up the entry the next time you generate them.
Before you start
-
A Vulnlog file that lists the releases the finding affects. To add a release, see Add and publish releases.
-
From the scanner: the vulnerability ID, the package URL (PURL) of the affected package, and the scanner’s name. A PURL identifies a package and its version, for example
pkg:maven/org.apache.commons/commons-text@1.9. Most scanners show it with the finding.
In this guide, Dependency-Check reports Text4Shell (CVE-2022-42889) in Acme Shop 4.2.0 and 4.3.0, and acme-shop.vl.yaml doesn’t have an entry for it yet.
Record the finding
-
Add the entry with
vulnlog modify add:$ vulnlog modify add acme-shop.vl.yaml --vuln-id CVE-2022-42889 --name Text4Shell \ --description "Remote code execution through string interpolation in Apache Commons Text" \ --release 4.2.0 --release 4.3.0 \ --package "pkg:maven/org.apache.commons/commons-text@1.9" \ --reporter dependency-check --tag backend --tag container Added: CVE-2022-42889 to acme-shop.vl.yamlVulnlog adds the entry at the top of
vulnerabilitiesand sets the report date to today:- id: CVE-2022-42889 name: Text4Shell description: Remote code execution through string interpolation in Apache Commons Text releases: - 4.2.0 - 4.3.0 packages: ["pkg:maven/org.apache.commons/commons-text@1.9"] reports: - reporter: dependency-check at: 2026-11-07 tags: - backend - containerPass at least the earliest release that has the finding. The entry also applies to every later release until it has a resolution. Without
--release, the entry gets the last release in the file. For all options, see vulnlog modify add. -
Commit the entry. It has no verdict yet, so its state is
under investigation, and the scanner keeps reporting the finding.
Record the verdict
-
Analyse the finding. Commons Text is only vulnerable through
StringSubstitutor, and Acme Shop never calls it. -
Run
vulnlog modify addagain with the same--vuln-id. Vulnlog updates the existing entry and keeps the fields you don’t pass:$ vulnlog modify add acme-shop.vl.yaml --vuln-id CVE-2022-42889 \ --analysis "Acme Shop only uses StringEscapeUtils from Commons Text. The server never calls StringSubstitutor, which performs the vulnerable interpolation." \ --analyzed-at 2026-11-07 --verdict "not affected" \ --justification "vulnerable code not in execute path" Updated: CVE-2022-42889 in acme-shop.vl.yamlThe entry now ends with your analysis and verdict:
analysis: >- Acme Shop only uses StringEscapeUtils from Commons Text. The server never calls StringSubstitutor, which performs the vulnerable interpolation. analyzed_at: 2026-11-07 verdict: not affected justification: vulnerable code not in execute pathPass the day you analysed the finding to
--analyzed-at.vulnlog validatewarns if it’s before the report date.Always pass
--justificationwith--verdict "not affected". Without it,modify addstill writes the entry, but every later command rejects the file withInvalid justification: null.
You can also edit the YAML by hand instead of running modify add.
Run vulnlog fmt afterwards.
See Validate and format files.
For every verdict, justification, severity, and disposition value, see Verdicts and justifications.
Variants
If the finding affects you and you’ll fix it
Record affected with a severity and the disposition will fix:
$ vulnlog modify add acme-shop.vl.yaml --vuln-id CVE-2022-22965 \
--analysis "Acme Shop runs as a Spring Boot executable JAR on JDK 17. The published exploit needs a WAR deployment on Apache Tomcat, but Spring advises all users to upgrade." \
--analyzed-at 2026-11-07 --verdict affected --severity medium --disposition "will fix"
The scanner keeps reporting the finding until you ship the fix. When you do, record the resolution. See Record a resolution.
If you need the scanner to pass until the fix ships
Add a temporary suppression to the report of the scanner that should stop failing.
modify add has no option for it, so edit the YAML.
Give the suppress block the last day the suppression applies:
reports:
- reporter: trivy
at: 2026-04-07
suppress:
expires_at: 2027-03-31
Up to and including that date, the generated suppression file contains the finding. From the next day on, it doesn’t, and the scanner reports the finding again.
If you accept the risk
Record affected with the disposition wont fix.
To keep the scanner quiet, add an empty suppress block to the report:
- id: CVE-2021-23337
description: Command injection through the template function in lodash
releases:
- 4.2.0
- 4.3.0
packages: ["pkg:npm/lodash@4.17.20"]
reports:
- reporter: npm-audit
at: 2026-03-10
suppress: {}
tags: [frontend]
analysis: >-
The template function is only used in the admin interface, with templates that administrators write. Administrators can
already change the shop configuration, so the injection gives them no additional access. The admin interface is removed
in Acme Shop 5.0.
analyzed_at: 2026-03-12
verdict: affected
severity: low
disposition: wont fix
For all suppression rules, see Suppression rules.
If your verdict changes
New information can change a verdict, for example a code change that now calls StringSubstitutor.
Run vulnlog modify add with the new verdict, a new analysis, and today’s date:
$ vulnlog modify add acme-shop.vl.yaml --vuln-id CVE-2022-42889 \
--analysis "The new template feature passes user input to StringSubstitutor." \
--analyzed-at 2026-11-08 --verdict affected --severity critical --disposition "will fix"
Updated: CVE-2022-42889 in acme-shop.vl.yaml
modify add keeps the justification of the old verdict, and vulnlog validate doesn’t report it.
Remove the justification line by hand.
In the other direction, from affected to not affected, remove severity and disposition and pass --justification.
Commit the change on its own, so the Git history shows the old and the new verdict.
If a customer or researcher reports a vulnerability
The vulnerability needs a CVE, GHSA, RUSTSEC, or Snyk ID. Vulnlog can’t record a finding without one, such as a flaw in your own code from a penetration test. See What Vulnlog leaves out.
Use the reporter other and say where the report came from in source.
modify add can’t set source, so add the report in the YAML.
An entry that modify add --reporter other writes fails validation with Generic reporter without source specified until you add source:
reports:
- reporter: other
at: 2026-07-02
source: Customer inquiry
If a scanner already reported the same vulnerability, add the report to the existing entry instead of creating a second entry.
Check the result
-
Validate the file:
$ vulnlog validate acme-shop.vl.yaml info: acme-shop.vl.yaml: releases[4.4.0]: Unreferenced release ID '4.4.0'. 1 info Validated: acme-shop.vl.yaml -
Generate the suppression file of the scanner and check that it contains the finding:
$ vulnlog suppress acme-shop.vl.yaml --reporter dependency-check -o - <!-- Generated by Vulnlog (https://vulnlog.dev). DO NOT EDIT. --> <suppressions xmlns="https://jeremylong.github.io/DependencyCheck/dependency-suppression.1.3.xsd"> <suppress> <notes>Acme Shop only uses StringEscapeUtils from Commons Text. The server never calls StringSubstitutor, which performs the vulnerable interpolation.</notes> <cve>CVE-2022-42889</cve> </suppress> </suppressions>
For how a verdict leads to a state in reports, see Vulnerability states.