Skip to content

tmatens/compose-lint

Follow this package

Get the evidence behind this dependency. Browse imported advisories below, or check an exact version against OSV now. View source coverage.

Check the version you ship.

Get a fresh OSV lookup for an exact release. We send the package name and version to OSV without storing a report.

Exact-version checks are not supported for this ecosystem yet.

Advisories & recorded fixes

low2.3
CVE-2026-123796Package fixes recorded

compose-lint: Incomplete fix for GHSA-jf3h-8jvx-vcrg: a run stopped at the finding limit quotes a secret from a CI-generated `.env`

This is an incomplete fix for GHSA-jf3h-8jvx-vcrg. 0.32.0 made findings quote the ${NAME} a sibling .env filled in, instead of its value. The same release added a stop at 20,000 findings per document, and that stop is checked before the quoting step. A run that hits it reports the findings graded so far with the resolved values still in them, in text, JSON and SARIF output. That happens with or without --allow-partial-coverage.

Recorded fixes — compose-lint: 0.33.0; tmatens/compose-lint: 0.33.0 or 691e08bd1881ada886e3f556d0793079e8114451. Check your release branch.

Public exploit reference

tmatens/compose-lint GitHub Actions
Affected range Recorded fix
From 0.32.0 before 0.33.0Ecosystem versions0.33.0
From 2d42617e4c6416f797bbfc6a057950131fa02df3 before 691e08bd1881ada886e3f556d0793079e8114451Git commits691e08bd1881ada886e3f556d0793079e8114451

Version evidence: OSV · GHSA-rm8w-w798-g545

View original version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0.32.0"
        },
        {
          "fixed": "0.33.0"
        }
      ],
      "type": "ECOSYSTEM"
    },
    {
      "events": [
        {
          "introduced": "2d42617e4c6416f797bbfc6a057950131fa02df3"
        },
        {
          "fixed": "691e08bd1881ada886e3f556d0793079e8114451"
        }
      ],
      "type": "GIT",
      "repo": "https://github.com/tmatens/compose-lint"
    }
  ],
  "versions": [
    "0.32.0",
    "v0.32.0"
  ]
}
low2.3
CVE-2026-123373Package fixes recorded

compose-lint: A committed symlink makes compose-lint quote a file from outside the project into its output

Like Docker Compose, compose-lint follows symlinks when it reads a project's files. Unlike Compose, compose-lint up to 0.24.0 could then put the contents of a file from outside the project into its output, where the author of a pull request can read it.

Recorded fixes — compose-lint: 0.25.0; tmatens/compose-lint: 0.25.0 or cb12b5313ff1fb182ff3c832b41ff3d574a68c6b. Check your release branch.

Exploitation not established

tmatens/compose-lint GitHub Actions
Affected range Recorded fix
From 0.2.0 before 0.25.0Ecosystem versions0.25.0
From 60c091c7cc8f86c6b0c5954031097364fea0a201 before cb12b5313ff1fb182ff3c832b41ff3d574a68c6bGit commitscb12b5313ff1fb182ff3c832b41ff3d574a68c6b

Version evidence: OSV · GHSA-whr6-fgpq-fpv9

View original version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0.2.0"
        },
        {
          "fixed": "0.25.0"
        }
      ],
      "type": "ECOSYSTEM"
    },
    {
      "events": [
        {
          "introduced": "60c091c7cc8f86c6b0c5954031097364fea0a201"
        },
        {
          "fixed": "cb12b5313ff1fb182ff3c832b41ff3d574a68c6b"
        }
      ],
      "type": "GIT",
      "repo": "https://github.com/tmatens/compose-lint"
    }
  ],
  "versions": [
    "v0.24.0",
    "v0.23.0",
    "v0.22.0",
    "v0.21.0",
    "v0.20.0",
    "v0.19.0",
    "v0.18.0",
    "v0.17.0",
    "v0.16.0",
    "v0.15.2",
    "v0.15.1",
    "v0.15.0",
    "v0.14.1",
    "v0.14.0",
    "v0.13.0",
    "v0.12.2",
    "v0.12.1",
    "v0.12.0",
    "v0.11.0",
    "v0.10.0",
    "v0.9.0",
    "v0.8.0",
    "v0.7.1",
    "v0.7.0",
    "v0.6.0",
    "v0.5.2",
    "v0.5.1",
    "v0.5.0",
    "v0.4.1",
    "v0.4.0",
    "v0.3.7",
    "v0.3.6",
    "v0.3.4",
    "v0.3.3",
    "v0.3.2",
    "v0.3.1",
    "v0.3.0",
    "v0.2.0"
  ]
}
low2.3
CVE-2026-123372Package fixes recorded

compose-lint: A pull request can make compose-lint quote a secret from a CI-generated `.env` into its findings

Since 0.22.0, compose-lint fills in ${VAR} references from the .env beside the Compose file, as Compose does. The documentation says values under environment: are never resolved from a .env, "that is where secrets live". But image: values are resolved, and CL-0004 and CL-0019 quote the resolved image in their message and fix text.

Recorded fixes — compose-lint: 0.32.0; tmatens/compose-lint: 0.32.0 or 2d42617e4c6416f797bbfc6a057950131fa02df3. Check your release branch.

Public exploit reference

tmatens/compose-lint GitHub Actions
Affected range Recorded fix
From 0.22.0 before 0.32.0Ecosystem versions0.32.0
From 811ef6b379dbc78d048fcedaf976205705d4a7c3 before 2d42617e4c6416f797bbfc6a057950131fa02df3Git commits2d42617e4c6416f797bbfc6a057950131fa02df3

Version evidence: OSV · GHSA-jf3h-8jvx-vcrg

View original version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0.22.0"
        },
        {
          "fixed": "0.32.0"
        }
      ],
      "type": "ECOSYSTEM"
    },
    {
      "events": [
        {
          "introduced": "811ef6b379dbc78d048fcedaf976205705d4a7c3"
        },
        {
          "fixed": "2d42617e4c6416f797bbfc6a057950131fa02df3"
        }
      ],
      "type": "GIT",
      "repo": "https://github.com/tmatens/compose-lint"
    }
  ],
  "versions": [
    "v0.31.0",
    "v0.30.0",
    "v0.29.0",
    "v0.28.0",
    "v0.27.0",
    "v0.26.0",
    "v0.25.0",
    "v0.24.0",
    "v0.23.0",
    "v0.22.0"
  ]
}
low2.3
CVE-2026-123371Package fixes recorded

compose-lint: A `.compose-lint.yml` symlinked outside the project is read, and a parse error quotes part of the target

compose-lint automatically reads a .compose-lint.yml policy file beside the Compose file. It is meant to read nothing outside the project directory, but it follows that file if it is a symlink, wherever it points.

Recorded fixes — compose-lint: 0.32.0; tmatens/compose-lint: 0.32.0 or 2d42617e4c6416f797bbfc6a057950131fa02df3. Check your release branch.

Exploitation not established

tmatens/compose-lint GitHub Actions
Affected range Recorded fix
From 0.2.0 before 0.32.0Ecosystem versions0.32.0
From 60c091c7cc8f86c6b0c5954031097364fea0a201 before 2d42617e4c6416f797bbfc6a057950131fa02df3Git commits2d42617e4c6416f797bbfc6a057950131fa02df3

Version evidence: OSV · GHSA-88f4-frh5-gmcr

View original version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0.2.0"
        },
        {
          "fixed": "0.32.0"
        }
      ],
      "type": "ECOSYSTEM"
    },
    {
      "events": [
        {
          "introduced": "60c091c7cc8f86c6b0c5954031097364fea0a201"
        },
        {
          "fixed": "2d42617e4c6416f797bbfc6a057950131fa02df3"
        }
      ],
      "type": "GIT",
      "repo": "https://github.com/tmatens/compose-lint"
    }
  ],
  "versions": [
    "v0.31.0",
    "v0.30.0",
    "v0.29.0",
    "v0.28.0",
    "v0.27.0",
    "v0.26.0",
    "v0.25.0",
    "v0.24.0",
    "v0.23.0",
    "v0.22.0",
    "v0.21.0",
    "v0.20.0",
    "v0.19.0",
    "v0.18.0",
    "v0.17.0",
    "v0.16.0",
    "v0.15.2",
    "v0.15.1",
    "v0.15.0",
    "v0.14.1",
    "v0.14.0",
    "v0.13.0",
    "v0.12.2",
    "v0.12.1",
    "v0.12.0",
    "v0.11.0",
    "v0.10.0",
    "v0.9.0",
    "v0.8.0",
    "v0.7.1",
    "v0.7.0",
    "v0.6.0",
    "v0.5.2",
    "v0.5.1",
    "v0.5.0",
    "v0.4.1",
    "v0.4.0",
    "v0.3.7",
    "v0.3.6",
    "v0.3.4",
    "v0.3.3",
    "v0.3.2",
    "v0.3.1",
    "v0.3.0",
    "v0.2.0"
  ]
}
medium5.3
CVE-2026-123369Package fixes recorded

compose-lint: Compose file text can issue GitHub Actions workflow commands through the compose-lint Action

The GitHub Actions runner treats certain text in a step's output as commands. The legacy form, ##[command], is recognized anywhere in a line. compose-lint's text report prints service names, environment keys and lines of the Compose file, and it does not neutralize ##[. Inside the compose-lint Action, a Compose file from a pull request can therefore:

Recorded fixes — tmatens/compose-lint: 0.31.0 or a6a7a76736de1c72abfa96c41ff8af556ffdc55f; compose-lint: 0.31.0. Check your release branch.

Exploitation not established

tmatens/compose-lint GitHub Actions
Affected range Recorded fix
From 0.2.0 before 0.31.0Ecosystem versions0.31.0
From 60c091c7cc8f86c6b0c5954031097364fea0a201 before a6a7a76736de1c72abfa96c41ff8af556ffdc55fGit commitsa6a7a76736de1c72abfa96c41ff8af556ffdc55f

Version evidence: OSV · GHSA-6f4g-xm8v-pgv6

View original version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0.2.0"
        },
        {
          "fixed": "0.31.0"
        }
      ],
      "type": "ECOSYSTEM"
    },
    {
      "events": [
        {
          "introduced": "60c091c7cc8f86c6b0c5954031097364fea0a201"
        },
        {
          "fixed": "a6a7a76736de1c72abfa96c41ff8af556ffdc55f"
        }
      ],
      "type": "GIT",
      "repo": "https://github.com/tmatens/compose-lint"
    }
  ],
  "versions": [
    "v0.30.0",
    "v0.29.0",
    "v0.28.0",
    "v0.27.0",
    "v0.26.0",
    "v0.25.0",
    "v0.24.0",
    "v0.23.0",
    "v0.22.0",
    "v0.21.0",
    "v0.20.0",
    "v0.19.0",
    "v0.18.0",
    "v0.17.0",
    "v0.16.0",
    "v0.15.2",
    "v0.15.1",
    "v0.15.0",
    "v0.14.1",
    "v0.14.0",
    "v0.13.0",
    "v0.12.2",
    "v0.12.1",
    "v0.12.0",
    "v0.11.0",
    "v0.10.0",
    "v0.9.0",
    "v0.8.0",
    "v0.7.1",
    "v0.7.0",
    "v0.6.0",
    "v0.5.2",
    "v0.5.1",
    "v0.5.0",
    "v0.4.1",
    "v0.4.0",
    "v0.3.7",
    "v0.3.6",
    "v0.3.4",
    "v0.3.3",
    "v0.3.2",
    "v0.3.1",
    "v0.3.0",
    "v0.2.0"
  ]
}
low3.1
CVE-2026-123368Package fixes recorded

compose-lint: .env read through a symlink outside the project can expose the CI job's environment

compose-lint fills in ${VAR} references from the .env file next to the Compose file. It is meant to read nothing outside the project directory, and env_file:, include: and extends: paths are checked for that. The .env read is not. If .env is a symlink, compose-lint follows it wherever it points.

Recorded fixes — compose-lint: 0.31.0; tmatens/compose-lint: 0.31.0 or a6a7a76736de1c72abfa96c41ff8af556ffdc55f. Check your release branch.

Exploitation not established

tmatens/compose-lint GitHub Actions
Affected range Recorded fix
From 0.22.0 before 0.31.0Ecosystem versions0.31.0
From 811ef6b379dbc78d048fcedaf976205705d4a7c3 before a6a7a76736de1c72abfa96c41ff8af556ffdc55fGit commitsa6a7a76736de1c72abfa96c41ff8af556ffdc55f

Version evidence: OSV · GHSA-6wcv-rj3c-mhv3

View original version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "0.22.0"
        },
        {
          "fixed": "0.31.0"
        }
      ],
      "type": "ECOSYSTEM"
    },
    {
      "events": [
        {
          "introduced": "811ef6b379dbc78d048fcedaf976205705d4a7c3"
        },
        {
          "fixed": "a6a7a76736de1c72abfa96c41ff8af556ffdc55f"
        }
      ],
      "type": "GIT",
      "repo": "https://github.com/tmatens/compose-lint"
    }
  ],
  "versions": [
    "v0.30.0",
    "v0.29.0",
    "v0.28.0",
    "v0.27.0",
    "v0.26.0",
    "v0.25.0",
    "v0.24.0",
    "v0.23.0",
    "v0.22.0"
  ]
}