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 ##[. 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: true
Run through the Action, this produces a fake error annotation and folds the remaining log lines, including the FAIL verdict, into a collapsed group.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | compose-lint | < 0.31.0 | 0.31.0 |
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
- https://github.com/tmatens/compose-lint/releases/tag/v0.31.0
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N- Weakness (CWE)
CWE-117, CWE-150- Platform
- Python (PyPI)
- Package
compose-lint- Disclosed
- 10.11.2026
- Updated
- 10.11.2026 18:17
Sources and licenses
OSV / GitHub Advisory Database - GHSA-6f4g-xm8v-pgv6 - CC BY 4.0
Vulnerability history: compose-lint
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 10
- First → latest
- 11.2026 11.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Medium 3
- Low 7
Disclosures per year
- 2026: 10
-
compose-lint: Compose file text can issue GitHub Actions workflow commands through the compose-lint Action this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.