CVE-2026-125121

Name of the Vulnerable Software and Affected Versions compose-lint versions prior to 0.32.0

Description An issue exists where untrusted input can be interpreted as workflow commands by CI runners. This occurs because the software fails to properly escape command openers in several scenarios: Unicode whitespace preceding :: is not escaped, JSON and SARIF formats printed to stdout are not sanitized, and certain command-line errors print raw arguments. Additionally, ##vso[ logging commands for Azure Pipelines are not escaped. This allows a malicious actor to create annotations, hide parts of job logs, or issue other runner commands via crafted Compose values, repository paths, or service names. The issue affects the compose-lint package, the pre-commit hook, and the Docker image when run directly in CI. The GitHub Action is only affected when the sarif-file: parameter points to a subdirectory that cannot be created.

Recommendations Update to version 0.32.0 or later. For GitHub Actions, use the tmatens/compose-lint Action or wrap the step with ::stop-commands::<random token> and ::<token>::. In the GitHub Action, keep the sarif-file at the workspace root (e.g., sarif-file: results.sarif). Redirect --format json and --format sarif output to a file instead of the log. End the pre-commit hook args: with -- and wrap the step with ::stop-commands:: in CI. On Azure Pipelines, avoid printing output from runs over untrusted pull requests to the job log.