CVE-2026-123369: compose-lint: Compose file text can issue GitHub Actions workflow commands through the compose-lint Action
Impact 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 ##[.
Published Nov 10, 2026
Affected packages
tmatens/compose-lint
- Ecosystem
- GitHub Actions
- Affected
- >= 0.2.0, <= 0.30.0
- Fixed in
- 0.31.0
compose-lint
- Ecosystem
- PyPI
- Affected
- <= 0.30.0
- Fixed in
- 0.31.0
- Check
pip show compose-lint
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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:
- create fake error or warning annotations on the pull request (
##[error],##[warning]) - fold the rest of the log, including the real verdict, out of sight (
##[group]) - blank out chosen strings for the rest of the log (
##[add-mask])
GitHub has postponed removing the deprecated set-output log command, so the runner still honors it. A test run of the Action on a GitHub-hosted runner confirmed that a ::set-output line from a Compose file is processed. Whether it can override the Action's own sarif-written output, which decides whether the SARIF upload step runs, has not been tested.
The exit code and the pass/fail result are not affected. Azure Pipelines parses the same ##[ syntax, so the pip package is listed for anyone printing the text report in other CI systems.
Found during an internal pre-1.0 security review.
Patches
Fixed in 0.31.0. The Action stops the runner from processing workflow commands while compose-lint's output is printed, using a random stop-commands token. The text report also escapes ##[, and :: at the start of a line, in anything taken from the Compose file.
Workarounds
- In your own workflow, wrap the compose-lint step in
::stop-commands::<random token>and::<random token>::. - Use
--format jsonor--format sarifrather than the text report when linting untrusted pull requests.
Reproduction
services:
web:
image: "nginx:1.25"
environment:
"##[error]DB_PASSWORD": placeholder
"##[group]svc":
image: "nginx:1.25"
privileged: trueRun through the Action, this produces a fake error annotation and folds the remaining log lines, including the FAIL verdict, into a collapsed group.
References
- https://github.com/tmatens/compose-lint/security/advisories/GHSA-6f4g-xm8v-pgv6
- https://nvd.nist.gov/vuln/detail/CVE-2026-123369
- https://github.com/tmatens/compose-lint/pull/918
- https://github.com/tmatens/compose-lint/commit/672bd11145621f787c295fb11f3a859cdec1b38d
- https://github.com/tmatens/compose-lint/releases/tag/v0.31.0
- https://github.com/advisories/GHSA-6f4g-xm8v-pgv6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More GitHub Actions vulnerabilities
All GitHub Actions entriesCVE-2026-123368
compose-lint: .env read through a symlink outside the project can expose the CI job's environment
low3.1Nov 10, 2026CVE-2026-123370
compose-lint: `fix --apply` can delete a line the user did not select, including a security setting
medium5.1Nov 10, 2026CVE-2026-123371
compose-lint: A `.compose-lint.yml` symlinked outside the project is read, and a parse error quotes part of the target
low2.3Nov 10, 2026CVE-2026-123372
compose-lint: A pull request can make compose-lint quote a secret from a CI-generated `.env` into its findings
low2.3Nov 10, 2026CVE-2026-123373
compose-lint: A committed symlink makes compose-lint quote a file from outside the project into its output
low2.3Nov 10, 2026CVE-2026-123796
compose-lint: Incomplete fix for GHSA-jf3h-8jvx-vcrg: a run stopped at the finding limit quotes a secret from a CI-generated `.env`
low2.3Nov 10, 2026
