Find what affects your release

In this tutorial, you find out which vulnerabilities affect Acme Shop 4.3.0 and compare them with the older release 4.2.0. Then you build the list of what the next release, 4.4.0, must fix. It takes about 10 minutes, and you don’t change the Vulnlog file.

Before you start

  • Install the Vulnlog CLI. For instructions, see Install Vulnlog.

  • Have a web browser to open the reports.

  • Create an empty directory and save the Acme Shop Vulnlog file in it as acme-shop.vl.yaml:

    acme-shop.vl.yaml
    # $schema: https://vulnlog.dev/schema/vulnlog-v1.json
    ---
    schemaVersion: "1"
    
    project:
      organization: Acme Corp
      name: Acme Shop
      author: Acme Product Security Team
      contact: security@acme.example
    
    tags:
      - id: backend
        description: Java server application
      - id: frontend
        description: Web user interface
      - id: worker
        description: Python report worker
      - id: container
        description: Container image that bundles all components
    
    releases:
      - id: 4.2.0
        published_at: 2026-03-02
        purls:
          - purl: "pkg:maven/com.acme/acme-shop-server@4.2.0"
            tags: [backend]
          - purl: "pkg:oci/acme-shop@sha256:cf9066b0fcef66d545007bd33b5d8d59e7434e37c2a23d19a3075fdb6f0b48b9"
            tags: [container]
      - id: 4.3.0
        published_at: 2026-06-15
        purls:
          - purl: "pkg:maven/com.acme/acme-shop-server@4.3.0"
            tags: [backend]
          - purl: "pkg:oci/acme-shop@sha256:23a5bff22a95119dc4bcef9422a20038eb3c2fd355f03928b02791273ff1cc27"
            tags: [container]
      - id: 4.4.0
        purls:
          - purl: "pkg:maven/com.acme/acme-shop-server@4.4.0"
            tags: [backend]
          - purl: "pkg:oci/acme-shop@sha256:350f97615163b67cbff8b015e60c77c2cbb954b4d9ffa9d48254e216e54899c8"
            tags: [container]
    
    vulnerabilities:
    
      - id: CVE-2023-32681
        description: Proxy-Authorization header leak in requests
        releases: [4.3.0]
        packages: ["pkg:pypi/requests@2.28.2"]
        reports:
          - reporter: github-dependabot
            at: 2026-07-14
        tags:
          - worker
          - container
    
      - id: CVE-2024-3094
        name: XZ Utils backdoor
        description: Backdoor in the liblzma library of XZ Utils
        releases: [4.3.0]
        packages: ["pkg:deb/debian/xz-utils@5.4.1"]
        reports:
          - reporter: other
            at: 2026-07-02
            source: Customer inquiry
        tags: [container]
        analysis: >-
          The container image is based on Debian 12, which ships xz-utils 5.4.1. The backdoor is only in the upstream releases 5.6.0
          and 5.6.1.
        analyzed_at: 2026-07-02
        verdict: not affected
        justification: vulnerable code not present
    
      - 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
    
      - 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.
    
      - id: CVE-2021-23337
        description: Command injection through the template function in lodash
        releases:
          - 4.2.0
          - 4.3.0
        packages: ["pkg:npm/lodash@4.17.20"]
        reports:
          - reporter: npm-audit
            at: 2026-03-10
            suppress: {}
        tags: [frontend]
        analysis: >-
          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.
        analyzed_at: 2026-03-12
        verdict: affected
        severity: low
        disposition: wont fix
    
      - 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

The file lists three releases. Acme Corp published 4.2.0 on 2 March 2026 and 4.3.0 on 15 June 2026. Release 4.4.0 has no published_at date, because it hasn’t shipped yet.

Run every command in this tutorial from the directory that contains acme-shop.vl.yaml.

Report on release 4.3.0

Generate an impact report as of release 4.3.0:

vulnlog report impact acme-shop.vl.yaml --as-of 4.3.0 -o acme-shop-4.3.0.html
Wrote: acme-shop-4.3.0.html

The --as-of option asks what a user of that release faces. The report includes 4.3.0 and every earlier release. A fix counts only if it shipped in 4.3.0 or earlier.

Open acme-shop-4.3.0.html in your browser. Under About, the Filter line reads as of=4.3.0. Under Summary, the State line counts 1 Open, 1 Investigating (the state under investigation), 1 Accepted, 1 Resolved, and 2 Not applicable.

Look at the State column of the table:

  • CVE-2022-22965 (Spring4Shell) is Open, with severity Medium and disposition Will fix. Acme Shop is affected and the team plans to fix it, but no release contains the fix yet.

  • CVE-2023-32681 is Investigating. Nobody has assessed yet whether the vulnerability affects Acme Shop.

  • CVE-2021-23337 is Accepted. Acme Shop is affected, and the team accepted the risk instead of fixing it. The Analysis text explains why.

  • CVE-2021-44228 (Log4Shell) is Resolved. The Releases column shows Fixed in 4.3.0.

  • CVE-2022-42889 and CVE-2024-3094 are Not applicable, because they don’t affect Acme Shop.

Compare with release 4.2.0

Generate the same report as of the older release:

vulnlog report impact acme-shop.vl.yaml --as-of 4.2.0 -o acme-shop-4.2.0.html
Wrote: acme-shop-4.2.0.html

Open acme-shop-4.2.0.html. The table has four entries instead of six, and two things changed:

  • CVE-2021-44228 (Log4Shell) is Open, with severity Critical. The fix shipped in 4.3.0, so it doesn’t protect anyone who still runs 4.2.0.

  • CVE-2023-32681 and CVE-2024-3094 are gone. They only concern 4.3.0, so they don’t affect a 4.2.0 user.

A customer who asks "Am I affected by Log4Shell?" gets a different answer depending on the release they run. The --as-of option gives you the answer for each release.

List what 4.4.0 must fix

Narrow the 4.3.0 report to the entries that still need work. Use --state once for each state you want:

vulnlog report impact acme-shop.vl.yaml --as-of 4.3.0 --state open --state "under investigation" -o acme-shop-4.4.0-todo.html
Wrote: acme-shop-4.4.0-todo.html

Open acme-shop-4.4.0-todo.html. Two entries remain:

  • CVE-2022-22965 (Spring4Shell), with verdict Affected and disposition Will fix.

  • CVE-2023-32681, which needs a verdict before you can decide whether 4.4.0 must fix it.

Check what each release fixed

The changelog report lists the fixes each release shipped. It prints to the terminal:

vulnlog report changelog acme-shop.vl.yaml
Acme Corp / Acme Shop

4.3.0 (2026-06-15)
  1 fixed: 1 critical
  CVE-2021-44228 (critical, also GHSA-jfh8-c2jp-5v3q) "Log4Shell" Remote code execution through JNDI lookups in Apache Log4j
    fix: Updated log4j-core from 2.14.1 to 2.17.1

Now ask for the fixes in 4.4.0:

vulnlog report changelog acme-shop.vl.yaml --fixed-in 4.4.0
info: no fixed vulnerabilities to report

No resolution is recorded for 4.4.0 yet. When the team fixes Spring4Shell and records the resolution, this command lists it, and you can paste the result into the release notes.

What you’ve learned

Now you can:

  • See a release the way its users see it with --as-of.

  • Narrow a report to the work that’s still open with --state.

  • List the fixes each release shipped with the changelog report.

Next steps