Troubleshooting
Each section starts with the message you see.
The examples use acme-shop.vl.yaml, and line numbers and IDs come from your own file.
File name must be [vulnlog|*.vl].[yaml|yml]
Usage: vulnlog validate [<options>] <inputs>...
Error: invalid value for <inputs>: Input 'acme-shop.yaml' is not valid: File name must be [vulnlog|*.vl].[yaml|yml]: acme-shop.yaml
This is the output of vulnlog validate acme-shop.yaml, which exits with code 1.
The CLI reads only files named vulnlog.yaml, vulnlog.yml, .vl.yaml, or .vl.yml.
Rename the file, for example to acme-shop.vl.yaml.
See File format.
Unsupported vulnerability ID
error: acme-shop.vl.yaml: 45:9: vulnerabilities[ACME-2026-001].id: Unsupported vulnerability ID: ACME-2026-001
The id, every alias, and every value in vuln_ids must start with CVE-, GHSA-, RUSTSEC-, or SNYK-.
Use the CVE ID if the vulnerability has one, or the GHSA ID otherwise.
Record internal ticket numbers in comment or in resolution.ref.
See Vulnerabilities.
A finding without one of these IDs can’t be an entry. See What Vulnlog leaves out.
Unknown property
error: acme-shop.vl.yaml: 69:18: vulnerabilities[CVE-2024-3094].analysed_at: Unknown property 'analysed_at'. Try updating vulnlog.
The file contains a key that the format doesn’t define.
Often it’s a spelling mistake.
Field names use American spelling, for example analyzed_at.
If the key is right, the file may need a newer version of Vulnlog.
See Install Vulnlog.
missing (therefore NULL) value for creator parameter
error: acme-shop.vl.yaml: 45:5: vulnerabilities[CVE-2023-32681].packages: YAML parse error: Instantiation of [simple type, class dev.vulnlog.lib.document.dto.VulnerabilityEntryDto] value failed for JSON property packages due to missing (therefore NULL) value for creator parameter packages which is a non-nullable type
A required field is missing.
The name after creator parameter is the field, here packages.
Add it to the object the path points to.
For the required fields, see Vulnerabilities and Project and releases.
Invalid verdict: under investigation
error: acme-shop.vl.yaml: 55:14: vulnerabilities[CVE-2023-32681].verdict: Invalid verdict: under investigation
An entry that is under investigation has no verdict.
Remove the verdict line.
The same message with another value means the value isn’t affected or not affected.
See Verdicts and justifications.
Invalid severity: null
error: acme-shop.vl.yaml: vulnerabilities[CVE-2022-22965].severity: Invalid severity: null
An entry with verdict: affected needs a severity: low, medium, high, or critical.
Add it below verdict.
Invalid justification: null
error: acme-shop.vl.yaml: vulnerabilities[CVE-2022-42889].justification: Invalid justification: null
An entry with verdict: not affected needs a justification.
Add one of the five values from Verdicts and justifications.
Disposition requires verdict 'affected'
error: acme-shop.vl.yaml: 72:18: vulnerabilities[CVE-2024-3094].disposition: Disposition requires verdict 'affected'.
disposition says what you plan to do about a vulnerability that affects you.
Remove it from entries that are not affected or have no verdict yet.
References undefined release
error: acme-shop.vl.yaml: vulnerabilities[CVE-2023-32681].releases: References undefined release '4.1.0'. Defined releases: 4.2.0, 4.3.0, 4.4.0
An entry’s releases or resolution.in names a release that isn’t in the top-level releases list.
Fix the value, or add the release.
See Add and publish releases.
If the defined releases show 5.1 where your file says 5.10, YAML read the unquoted ID as a number.
Quote the ID in releases, for example id: "5.10".
See Project and releases.
Duplicate vulnerability ID
error: acme-shop.vl.yaml: vulnerabilities[CVE-2022-22965]: Duplicate vulnerability ID 'CVE-2022-22965'.
Two entries have the same id.
A Vulnlog file has one entry per vulnerability.
Merge the two entries: keep one, and move the reports, releases, packages, and tags of the other into it.
Cannot deserialize value of type java.time.LocalDate
error: acme-shop.vl.yaml: 23:19: releases[4.2.0].published_at: YAML parse error: Cannot deserialize value of type `java.time.LocalDate` from String "2026-3-2": ...
A date isn’t in the format YYYY-MM-DD.
Write the month and the day with two digits, for example 2026-03-02.
Unsupported reporter
error: acme-shop.vl.yaml: 101:19: vulnerabilities[CVE-2022-22965].reports[0].reporter: Unsupported reporter: trivvy
The reporter of a report isn’t one of the supported values.
For a source that isn’t a supported scanner, use other with a source.
See Supported scanners.
Invalid reporter is the same problem in the --reporter option.
The command exits with code 5, and the hint lists the supported reporters.
Unsupported PURL
error: acme-shop.vl.yaml: 79:16: vulnerabilities[CVE-2022-42889].packages[0]: Unsupported PURL: pkgx:maven/org.apache.commons/commons-text@1.9
A package URL (PURL) in packages or in a release’s purls isn’t valid.
A PURL starts with pkg:, and some types need more parts.
For example, a Maven PURL needs the group ID, as in pkg:maven/org.apache.commons/commons-text@1.9.
Copy the PURL from the scanner’s finding, or check it against the PURL specification.
Unsupported schema version
error: acme-shop.vl.yaml: 3:16: schemaVersion: Unsupported schema version '2'. Try updating vulnlog.
The file uses a version of the format that your Vulnlog version doesn’t know. Update Vulnlog. See Install Vulnlog.
Empty YAML document
error: acme-shop.vl.yaml: Empty YAML document
The file is empty. To create a Vulnlog file, see vulnlog init.
References undefined tags
error: acme-shop.vl.yaml: vulnerabilities[CVE-2023-32681].tags[workers]: References undefined tags 'workers'. Defined tags: backend, container, frontend, worker
An entry or a release package URL (PURL) uses a tag that isn’t defined in tags.
The message lists the tags the file defines.
Fix the spelling, or add the tag.
See Tags.
Generic reporter without source specified
error: acme-shop.vl.yaml: vulnerabilities[CVE-2024-3094]: Generic reporter without source specified.
A report with reporter: other needs a source that says who reported the vulnerability, for example source: Customer inquiry.
not canonically formatted
warning: acme-shop.vl.yaml: not canonically formatted
[non-canonical-array-style] vulnerabilities[CVE-2023-32681].releases: Line 48: canonical style for this list is a flow array, e.g. key: [value].
vulnlog fmt --check found a difference from the canonical style and exits with code 3.
The file is still valid.
Run vulnlog fmt acme-shop.vl.yaml to rewrite it.
See Validate and format files.
contains YAML comments; they are removed on write
warning: acme-shop.vl.yaml: contains YAML comments; they are removed on write
hint: record notes in schema fields (e.g. comment, analysis)
Commands that write the file remove every YAML comment except the schema header.
vulnlog fmt --check reports the same problem as [comments-not-preserved].
Before you run the command, move each note into a field.
For the fields that take notes, see File format.
-o requires a single reporter
error: -o requires a single reporter, found: dependency-check, github-dependabot, grype, npm-audit, trivy
hint: use --reporter <name> to pick one, or --output-dir for one file per reporter
vulnlog suppress -o writes one file, but the file has reports from several reporters.
Add --reporter, or use --output-dir to write one file per reporter.
See vulnlog suppress.
Release not found
error: Release not found: 4.5.0
hint: Known releases: 4.2.0, 4.3.0, 4.4.0
The value of --as-of isn’t a release id in the file.
Use one of the releases in the hint.
Tag not found means the same for --tag.
The command exits with code 5.
See Filter options.
The scanner still reports a finding
Run suppress with -v to see which entries it left out, and why:
$ vulnlog -v suppress acme-shop.vl.yaml
| Message | Cause |
|---|---|
|
The entry has a resolution. If the scanner still reports it, the code it scans doesn’t contain the fix yet. |
|
|
|
The format can’t hold this ID type.
This line is an illustration, because Acme Shop has no Snyk report.
Add the scanner’s ID to the report’s |
|
Reporter |
If no line names the entry, check that it qualifies at all.
An entry that isn’t not affected needs a suppress block on the scanner’s report.
For the full rules, see Suppression rules.
If the generated file lists the finding, check that the scanner reads the file. For how to pass the file to each scanner, see Generate suppression files.
Ask for help
If your problem isn’t listed, ask in Q&A discussions. Error messages link there too.