vulnlog report changelog

vulnlog report changelog lists the vulnerabilities each release fixed, newest release first, as text or Markdown. Several Vulnlog files are merged into one report.

Synopsis

vulnlog report changelog <inputs>... [-o <path>] [--fixed-in <release-id>] [--format text|markdown] [--brief] [<filter-options>]

Arguments and options

Name Value Default Description

<inputs>

One or more Vulnlog files, or -

required

Files to report on, all with the same project block. For how files are merged, see Input files. - reads one file from stdin.

-o, --output

A file path, or -

stdout

File to write. - writes to stdout.

--fixed-in

A release ID

all releases

List only the vulnerabilities this release fixed.

--format

text or markdown

text

text is for reading in a terminal. markdown writes a [<release>] - <date> section, or [<release>] - unreleased for a release without published_at, with a # Security subsection for each release, to paste into a changelog file.

--brief

none

off

List only the IDs, aliases, and severities.

--reporter, --as-of, --tag

See Filter options

Select the entries. With --as-of, a fix in a later release isn’t listed.

For global options and standard input and output, see Global options and Standard input and output.

Output

An entry appears under the release named in its resolution.in. An entry without a resolution doesn’t appear. An entry doesn’t appear either if none of its releases comes before the release in resolution.in, because no release shipped with the vulnerability.

Each release shows its ID and published_at date, or unreleased without a date, and a line that counts the fixes by severity.

Each entry shows its ID, its severity, and its aliases. A not affected entry shows not affected in place of the severity. Without --brief, it also shows the name and description of the entry, and the note and ref of its resolution. For these fields, see Vulnerabilities.

If no entry qualifies, the command writes nothing, prints info: no fixed vulnerabilities to report unless -q is set, and exits with 0.

The report contains no timestamp, so the same input always gives the same output.

Exit codes

Code When

0

The report was written, or no entry qualified.

1

A general error, or --format has an unknown value. For the general errors, see Exit codes.

2

A file doesn’t pass validation, or the files have different project blocks.

5

--fixed-in or a filter names an unknown release, reporter, or tag.

Examples

Report every release that fixed a vulnerability:

$ 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

Report release 4.3.0 as Markdown:

$ vulnlog report changelog acme-shop.vl.yaml --fixed-in 4.3.0 --format markdown
## [4.3.0] - 2026-06-15

### Security

_1 fixed: 1 critical_

- **CVE-2021-44228** (critical, also GHSA-jfh8-c2jp-5v3q): "Log4Shell" Remote code execution through JNDI lookups in Apache Log4j. Updated log4j-core from 2.14.1 to 2.17.1.

List the IDs only:

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

4.3.0 (2026-06-15)
  1 fixed: 1 critical
  CVE-2021-44228 (critical, also GHSA-jfh8-c2jp-5v3q)

Release 4.4.0 has no fix yet:

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

Once the Spring4Shell entry records resolution.in: 4.4.0, the report lists 4.4.0 as unreleased until you set its published_at:

$ vulnlog report changelog acme-shop.vl.yaml
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

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

Write the Markdown report to a file:

$ vulnlog report changelog acme-shop.vl.yaml --format markdown -o security-changelog.md
Wrote: security-changelog.md