Suppression

A suppression file tells a scanner to stop reporting a finding. vulnlog suppress generates one for each reporter in your Vulnlog file. The suppress block on a report and the suppression rules decide which entries go into it.

Synopsis

    reports:
      - reporter: trivy
        at: 2026-04-07
        suppress:
          expires_at: 2027-03-31

suppress

suppress is an optional object on a report. It applies only to the suppression file of that report’s reporter. See Report.

Field Type Required Default Description

expires_at

Date, YYYY-MM-DD

No

Never expires

Last day of the suppression. From the next day on, the entry no longer appears in the suppression file of that report’s reporter.

An empty block suppresses a finding without an end date:

        suppress: {}

Suppression rules

Vulnlog checks each report of each entry against these rules, in order. The first rule that applies decides.

  1. The entry is resolved: never suppressed. With --as-of, the resolution counts only if its release is part of the selection.

  2. suppress.expires_at is in the past: not suppressed.

  3. The verdict is not affected: suppressed for every reporter of the entry, with or without a suppress block.

  4. Any other entry: suppressed only for a report that has a suppress block.

See States.

Identifiers

A suppression file lists the IDs in the report’s vuln_ids. Without vuln_ids, it lists the entry’s id. It never lists aliases.

Each native format accepts only some ID types, shown in the table below. Vulnlog leaves out IDs that the format can’t hold. With -v, the command shows each one it leaves out. This line is an illustration, because Acme Shop has no Snyk report:

verbose: skipped CVE-2021-23337 for .snyk: the snyk format requires SNYK ids

Supported scanners

The reporter value decides which suppression file an entry goes into. Reporters with a native format get a file in the scanner’s own format. Every other reporter except other gets a file in the generic Vulnlog JSON format.

reporter Scanner Suppression file IDs in the file

trivy

Trivy

.trivyignore.yaml

CVE, GHSA

snyk

Snyk

.snyk

SNYK

dependency-check

OWASP Dependency-Check

dependency-check-suppressions.xml

CVE

cargo-audit

cargo-audit

audit.toml

RUSTSEC

grype

Grype

grype.generic.json

CVE, GHSA, RUSTSEC, SNYK

semgrep

Semgrep

semgrep.generic.json

CVE, GHSA, RUSTSEC, SNYK

npm-audit

npm audit

npm-audit.generic.json

CVE, GHSA, RUSTSEC, SNYK

github-dependabot

GitHub Dependabot

github-dependabot.generic.json

CVE, GHSA, RUSTSEC, SNYK

other

Any other source, such as a customer or a penetration test

None

None

In the generic format, the file of a reporter is <reporter>.generic.json, for example trivy.generic.json.

Every format except audit.toml carries the entry’s analysis as the reason and the expiry date. The audit.toml file lists only the IDs.

For the --format option and the files the command writes, see vulnlog suppress.

Generic format

A generic suppression file is a JSON object with one key, vulnerabilities. It holds one object for each ID, so an entry with two IDs in vuln_ids gets two objects.

Field Type Description

id

String

The vulnerability ID.

expires_at

Date, YYYY-MM-DD

The last day of the suppression. Left out when the suppress block has no expires_at.

statement

String

The entry’s analysis. An empty string when the entry has no analysis.

The generated npm-audit.generic.json for the lodash entry, which is suppressed without an end date:

{
  "vulnerabilities" : [ {
    "id" : "CVE-2021-23337",
    "statement" : "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."
  } ]
}

Examples

The Spring4Shell entry has the verdict affected. Its Trivy report is suppressed until 31 March 2027:

  - 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.

The generated .trivyignore.yaml:

# 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.

The Text4Shell entry has the verdict not affected, so its Dependency-Check report is suppressed without a suppress block:

  - 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-05-20
    tags:
      - backend
      - container
    analysis: >-
      Acme Shop only uses StringEscapeUtils from Commons Text. The server never calls StringSubstitutor, which performs the vulnerable
      interpolation.
    analyzed_at: 2026-05-21
    verdict: not affected
    justification: vulnerable code not in execute path

The generated dependency-check-suppressions.xml:

<!-- 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>

The Log4Shell entry’s Grype report has no suppress block, so grype.generic.json doesn’t list it. The XZ Utils entry has only an other report, so no suppression file lists it.