Vulnerabilities
Each item in vulnerabilities is an entry.
An entry records one vulnerability: the releases and packages it concerns, who reported it, your verdict, and, once it’s fixed, the resolution.
Synopsis
The Log4Shell entry from the Acme Shop file shows most fields:
- id: CVE-2021-44228
name: Log4Shell
description: Remote code execution through JNDI lookups in Apache Log4j
aliases: [GHSA-jfh8-c2jp-5v3q]
releases: [4.2.0]
packages: ["pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1"]
reports:
- reporter: grype
at: 2026-03-10
- reporter: other
at: 2026-03-11
source: Customer support request
tags:
- backend
- container
analysis: >-
The server logs the User-Agent header with log4j-core 2.14.1. A crafted header triggers a JNDI lookup and runs attacker-controlled
code.
analyzed_at: 2026-03-11
verdict: affected
severity: critical
disposition: will fix
resolution:
in: 4.3.0
at: 2026-06-15
note: Updated log4j-core from 2.14.1 to 2.17.1
Entry
Fields are listed in the order vulnlog fmt writes them.
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
|
String, vulnerability ID |
Yes |
None |
Primary identifier.
It must start with |
|
String |
No |
None |
Common name, for example |
|
String |
No |
None |
Short description of the vulnerability. |
|
List of vulnerability IDs |
No |
None |
Other IDs of the same vulnerability, for example its GHSA ID.
The same prefixes as for |
|
List of release IDs |
Yes |
None |
Releases in which the vulnerability was found.
The entry also applies to every release listed after the earliest of them, until the release in |
|
List of PURLs |
Yes |
None |
The package URLs (PURLs) of the dependencies that contain the vulnerability. Your scanner’s output usually includes them. |
|
List of report entries |
Yes |
None |
One report for each scanner or other source that reported the vulnerability. |
|
List of tag IDs |
No |
No tags |
Tags for filtering and for matching release PURLs.
Each tag must be defined in |
|
String |
No |
None |
Your reasoning behind the verdict. Suppression files and the impact report include it. So do OpenVEX documents, which tell your customers' tools whether a release is affected by a vulnerability. |
|
Date, |
No |
None |
Date of the analysis. |
|
|
No |
No verdict |
Whether the vulnerability affects your software. See Verdicts and justifications. |
|
|
With |
None |
Severity for your software. |
|
|
No |
Not stated |
What you plan to do.
Allowed only with |
|
One of five values |
With |
None |
Why the vulnerability doesn’t affect your software.
Allowed only with |
|
No |
None |
The release that fixes the vulnerability. |
|
|
String |
No |
None |
Any other note. Generated output doesn’t include it. |
Report
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
|
One of the reporter values |
Yes |
None |
The scanner or source that reported the vulnerability. For the values and the suppression file each one gets, see Supported scanners. |
|
Date, |
No |
None |
Date of the report. |
|
String |
With |
None |
Who or what reported the vulnerability, for example |
|
List of vulnerability IDs |
No |
The entry’s |
IDs this scanner uses for the vulnerability.
The suppression file for this reporter lists them instead of |
|
Object |
No |
None |
Suppresses the finding for this reporter. See Suppression. |
Resolution
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
|
Release ID |
Yes |
None |
The release that fixes the vulnerability.
It must be defined in |
|
Date, |
No |
None |
Date of the resolution. |
|
String, URI |
No |
None |
Link to the issue, pull request, or ticket that resolves the vulnerability. Release notes show it. |
|
String |
No |
None |
How you fixed it, for example |
For what a resolution does to the state and the suppression files, see States and Suppression rules.
Rules
vulnlog validate checks these rules.
| Rule | Level | Message |
|---|---|---|
|
Error |
|
|
Error |
|
Each |
Error |
|
No alias is the |
Error |
|
No alias appears in two entries. |
Error |
|
Each release in |
Error |
|
Each package is a valid PURL. |
Error |
|
Each tag is defined. |
Error |
|
|
Error |
|
A report with |
Error |
|
Dates use the format |
Error |
|
|
Warning |
|
If releases declare PURLs, each OpenVEX statement for the entry has a date.
The date comes from |
Warning |
|
Rules for verdict, severity, disposition, and justification are on Verdicts and justifications.
Examples
A minimal entry has only the four required fields.
This is Acme Shop’s entry for a Dependabot finding that nobody has analysed yet, without its description and tags:
- id: CVE-2023-32681
releases: [4.3.0]
packages: ["pkg:pypi/requests@2.28.2"]
reports:
- reporter: github-dependabot
Spring4Shell affects 4.2.0 and 4.3.0.
The Trivy finding is suppressed until 31 March 2027, and comment names the release planned for the fix:
- id: CVE-2022-22965
name: Spring4Shell
description: Remote code execution through data binding in Spring Framework
releases:
- 4.2.0
- 4.3.0
packages: ["pkg:maven/org.springframework/spring-beans@5.3.15"]
reports:
- reporter: trivy
at: 2026-04-07
suppress:
expires_at: 2027-03-31
tags:
- backend
- container
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-04-08
verdict: affected
severity: medium
disposition: will fix
comment: Planned for 4.4.0 together with the Spring Boot update.