Record a resolution

Record the release that fixes a vulnerability, so your reports show it as resolved, your release notes list the fix, and your suppression files stop hiding the finding.

Before you start

  • A triaged entry in your Vulnlog file. See Triage a new scanner finding.

  • The release that ships the fix, listed in releases. It doesn’t need to be published yet.

In this guide, Acme Shop updates spring-beans for 4.4.0, which fixes Spring4Shell (CVE-2022-22965).

Record the resolution

  1. Add a resolution to the entry, after disposition and before comment. in names the release with the fix. at is the date of the resolution, and note says what you changed:

        verdict: affected
        severity: medium
        disposition: will fix
        resolution:
          in: 4.4.0
          at: 2026-11-02
          note: Updated spring-beans from 5.3.15 to 5.3.18
        comment: Planned for 4.4.0 together with the Spring Boot update.

    modify add can’t set a resolution, so edit the YAML. To link the issue or pull request of the fix, add ref with its URL. For all resolution fields, see Vulnerabilities.

  2. Validate and format the file:

    $ vulnlog validate acme-shop.vl.yaml
    Validated: acme-shop.vl.yaml
    $ vulnlog fmt acme-shop.vl.yaml
    Unchanged: acme-shop.vl.yaml
  3. Regenerate the suppression files. Vulnlog never suppresses a resolved entry, so the Trivy file no longer contains Spring4Shell:

    $ vulnlog suppress acme-shop.vl.yaml --reporter trivy -o -
    # Generated by Vulnlog (https://vulnlog.dev). DO NOT EDIT.
    ---
    vulnerabilities: []

Variants

If the scanner checks a release without the fix

To keep the suppression until the release with the fix ships, generate the suppression file as of the release the scanner checks. See If you scan a release without the fix.

If you updated a dependency that never affected you

Record the resolution on a not affected entry in the same way. The entry’s state changes from not applicable to resolved, and the release notes list the update:

    verdict: not affected
    justification: vulnerable code not in execute path
    resolution:
      in: 4.4.0
      at: 2026-11-02
      note: Updated commons-text from 1.9 to 1.10.0

Once the entry is resolved, its suppression ends too. After the update, the scanner no longer reports the finding. Set at. OpenVEX documents, which tell your customers' tools whether a release is affected by a vulnerability, use it to date the statement. Without it, vulnlog validate warns that the entry leaves its VEX statement undated until the release has a published_at date.

Check the result

  • The changelog lists the fix under its release:

    $ vulnlog report changelog acme-shop.vl.yaml --fixed-in 4.4.0
    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 impact report shows the entry as Resolved (the state resolved), with Fixed in 4.4.0 in the Releases column. See Generate reports.

  • After you ship the fix, the scanner no longer reports the finding. If it still does, check that the scanner scans a build that contains the fix. See The scanner still reports a finding.

To write the security section of your release notes, see Write release notes. For how a resolution changes the state of an entry, see Vulnerability states.