compose-lint: File paths embedded in pull requests can inject CI workflow commands through command-line error messages
Impact
0.31.0 fixed GHSA-6f4g-xm8v-pgv6, where text from a Compose file became GitHub Actions workflow commands in compose-lint's output. The fix escapes the command openers in compose-lint's own output, but not in the argument parser's error messages. When a repository path reaches compose-lint's arguments without a -- before it, the argument parser prints it raw in its error message. That includes a carriage return, which the runner treats as a line break, so a command can also start a new line there.
A pull request can therefore create annotations, fold or hide parts of the job log, or issue other commands the runner accepts, when CI runs compose-lint over it, before anyone reviews it. The pass/fail result is not changed.
Affected setups pass repository paths to compose-lint without a -- before them: the pre-commit hook when args: is set without the documented trailing --, or the compose-lint package or Docker image called that way in a workflow. The pre-commit hook's default configuration passes -- and is not affected. The GitHub Action turns command processing off around each compose-lint run, so it is not affected.
Found during an internal pre-1.0 security review. It was first published as part of GHSA-r7j4-crjv-h467, together with four other gaps in the same fix. Each gap now has its own advisory.
Docker image. composelint/compose-lint tag 0.31.0 and the matching minor tag are affected, as was latest while it pointed to 0.31.0.
Releases before 0.31.0 are covered by GHSA-6f4g-xm8v-pgv6.
Patches
Fixed in 0.32.0. The argument parser's messages go through the same sanitizer as the rest of compose-lint's output.
Workarounds
- Upgrade to 0.32.0 or later.
- End the pre-commit hook's
args:with--, and put--before file paths when calling compose-lint directly. - On GitHub Actions, use the
tmatens/compose-lintAction, or bracket the compose-lint step with::stop-commands::<random token>and::<token>::, as the Action does.
Reproduction
On compose-lint 0.31.0 on a GitHub-hosted runner (runner 2.337.0), compose-lint '--##[warning]X/compose.yml' with no -- creates an annotation. The same path after -- creates none. The composelint/compose-lint:0.31.0 image produces byte-identical output to the package.
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.32.0 | 0.32.0 |
References
- https://github.com/tmatens/compose-lint/security/advisories/GHSA-8v59-qmwv-4p6q
- https://nvd.nist.gov/vuln/detail/CVE-2026-125123
- https://github.com/tmatens/compose-lint/pull/945
- https://github.com/tmatens/compose-lint/commit/542e63126f795564a65c63887ea0dc558a500688
- https://github.com/tmatens/compose-lint
- https://github.com/tmatens/compose-lint/releases/tag/v0.32.0
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N- Weakness (CWE)
CWE-117, CWE-150- Platform
- Python (PyPI)
- Package
compose-lint- Disclosed
- 10.11.2026
- Updated
- 11.11.2026 00:17
Sources and licenses
OSV / GitHub Advisory Database - GHSA-8v59-qmwv-4p6q - 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: File paths embedded in pull requests can inject CI workflow commands through command-line error messages 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.