Track a vulnerability to its fix
In this tutorial, you record a vulnerability that affects Acme Shop and follow it until a release fixes it. You keep the scanner quiet while the fix is planned, record the fix, and see what changes in the impact report, the suppression file, and the changelog. It takes about 15 minutes.
The vulnerability is Spring4Shell (CVE-2022-22965), a remote code execution vulnerability in the Spring Framework.
Trivy reported it in spring-beans 5.3.15, which Acme Shop 4.3.0 ships.
Before you start
-
Install the Vulnlog CLI. For instructions, see Install Vulnlog.
-
Have a web browser to open the reports.
You don’t need Trivy.
Create the Vulnlog file
Create an empty directory for the project:
mkdir acme-shop
cd acme-shop
Run every command in this tutorial from this directory.
Create a Vulnlog file:
vulnlog init --organization "Acme Corp" --name "Acme Shop" --author "Acme Product Security Team" -o vulnlog.yaml
Created: vulnlog.yaml
Open vulnlog.yaml in your editor.
Replace the line releases: [] with two releases:
releases:
- id: 4.3.0
published_at: 2026-06-15
- id: 4.4.0
Release 4.3.0 is the one your customers run.
Release 4.4.0 has no published_at date, because it hasn’t shipped yet.
Record the finding and your verdict
Suppose you’ve analysed the finding. The published exploit doesn’t work against Acme Shop, but Spring advises all users to upgrade. You rate the risk as medium and plan a fix.
Record the finding, the verdict affected, your severity, and your plan in one command:
vulnlog modify add vulnlog.yaml --vuln-id CVE-2022-22965 \
--name Spring4Shell \
--description "Remote code execution through data binding in Spring Framework" \
--release 4.3.0 \
--package "pkg:maven/org.springframework/spring-beans@5.3.15" \
--reporter trivy \
--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." \
--verdict affected --severity medium --disposition "will fix"
Added: CVE-2022-22965 to vulnlog.yaml
The --package value is a package URL (PURL), a standard way to name a package, its ecosystem, and its version in one string.
Vulnlog adds an entry to vulnerabilities:
- id: CVE-2022-22965
name: Spring4Shell
description: Remote code execution through data binding in Spring Framework
releases: [4.3.0]
packages: ["pkg:maven/org.springframework/spring-beans@5.3.15"]
reports:
- reporter: trivy
at: 2026-11-07
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.
verdict: affected
severity: medium
disposition: will fix
Your file shows the date you ran the command as the report date at.
See the open entry
Generate the impact report:
vulnlog report impact vulnlog.yaml
Wrote: vulnlog-impact-report.html
Open vulnlog-impact-report.html in your browser.
The table has one row.
CVE-2022-22965 is Open, with Severity Medium and Disposition Will fix.
The Releases column shows 4.3.0.
An entry is open when it affects you and no release fixes it yet.
Keep the scanner quiet until the fix ships
Generate the suppression file for Trivy:
vulnlog suppress vulnlog.yaml
Vulnlog prints the full path of the file it writes:
Wrote: /home/you/acme-shop/.trivyignore.yaml
Open .trivyignore.yaml:
# Generated by Vulnlog (https://vulnlog.dev). DO NOT EDIT.
---
vulnerabilities: []
The list is empty. Vulnlog doesn’t suppress a vulnerability that affects you unless you ask for it, so Trivy keeps reporting Spring4Shell.
The fix is planned, and you don’t want the finding to fail every build until then.
In vulnlog.yaml, add a suppress block with an end date to the Trivy report:
reports:
- reporter: trivy
at: 2026-11-07
suppress:
expires_at: 2027-03-31
Keep your own report date in at.
Save the file and generate the suppression file again:
vulnlog suppress vulnlog.yaml
Wrote: /home/you/acme-shop/.trivyignore.yaml
Now .trivyignore.yaml lists the finding, with your analysis as the reason:
# Generated by Vulnlog (https://vulnlog.dev). DO NOT EDIT.
---
vulnerabilities:
- id: CVE-2022-22965
expired_at: 2027-03-31
statement: >-
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.
31 March 2027 is the last day of the suppression. If the fix hasn’t shipped by then, Trivy reports the finding again.
Record the fix
Suppose the team updates spring-beans for release 4.4.0.
In vulnlog.yaml, add a resolution to the entry, below disposition:
verdict: affected
severity: medium
disposition: will fix
resolution:
in: 4.4.0
at: 2026-11-07
note: Updated spring-beans from 5.3.15 to 5.3.18
Save the file and check it:
vulnlog validate --strict vulnlog.yaml
Validated: vulnlog.yaml
See what the fix changed
Generate the impact report again:
vulnlog report impact vulnlog.yaml
Wrote: vulnlog-impact-report.html
Reload the report in your browser.
CVE-2022-22965 is now Resolved, and the Releases column shows Fixed in 4.4.0.
You didn’t set the state.
Vulnlog worked it out from the resolution.
Your customers still run 4.3.0, which doesn’t have the fix. Generate the report as of that release:
vulnlog report impact vulnlog.yaml --as-of 4.3.0 -o acme-shop-4.3.0.html
Wrote: acme-shop-4.3.0.html
Open acme-shop-4.3.0.html.
Under About, the Filter line reads as of=4.3.0, and CVE-2022-22965 is Open.
A fix in a later release doesn’t help a user of 4.3.0.
Generate the suppression file again:
vulnlog suppress vulnlog.yaml
Wrote: /home/you/acme-shop/.trivyignore.yaml
Open .trivyignore.yaml.
The list is empty again:
# Generated by Vulnlog (https://vulnlog.dev). DO NOT EDIT.
---
vulnerabilities: []
Vulnlog never suppresses a resolved entry. When Trivy scans 4.4.0 and stays quiet, you know the fix works.
Publish the release
The changelog report lists the fixes of each release:
vulnlog report changelog vulnlog.yaml
Acme Corp / Acme Shop
4.4.0 (unreleased)
1 fixed: 1 medium
CVE-2022-22965 (medium) "Spring4Shell" Remote code execution through data binding in Spring Framework
fix: Updated spring-beans from 5.3.15 to 5.3.18
The fix line is the note of your resolution.
Suppose release 4.4.0 ships.
In vulnlog.yaml, give the release its date:
releases:
- id: 4.3.0
published_at: 2026-06-15
- id: 4.4.0
published_at: 2026-11-07
Save the file and run the changelog report again:
vulnlog report changelog vulnlog.yaml
Acme Corp / Acme Shop
4.4.0 (2026-11-07)
1 fixed: 1 medium
CVE-2022-22965 (medium) "Spring4Shell" Remote code execution through data binding in Spring Framework
fix: Updated spring-beans from 5.3.15 to 5.3.18
You can paste these lines into the release notes of 4.4.0.
What you’ve learned
Now you can:
-
Record a vulnerability that affects you, with a severity and a plan.
-
Suppress a finding until a date, and let the suppression end when the fix is recorded.
-
Record a resolution and see the state change from
opentoresolved. -
See a release the way its users see it with
--as-of.
Next steps
-
Learn to read every part of the impact report in Read the impact report.
-
Keep a suppression for a scanner that still checks 4.3.0 with Generate suppression files.
-
Accept a risk instead of fixing it with Triage a new scanner finding.
-
Learn how a state follows from what you recorded in Vulnerability states.