# CVE-2026-125124: compose-lint insufficient CI command sanitization

Source: https://junglewise.ai/threats/cve-2026-125124-compose-lint-is-a-docker-compose-security-linter-that-identifies  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-125124 · Severity: info · Published 2026-11-10

compose-lint is a Docker Compose security linter that checks container configurations for dangerous settings before deployment. In version 0.31.0, the tool fails to properly neutralize Azure Pipelines workflow command syntax in its output, allowing a malicious Docker Compose file or pull request to inject arbitrary logging commands that execute within the CI/CD pipeline.

Technologies: [Tmatens Compose-Lint](https://junglewise.ai/threats/technologies/tmatens-compose-lint). Vendors: [Tmatens](https://junglewise.ai/threats/vendors/tmatens).

## Quick answers

**Is CVE-2026-125124 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-125124 being exploited in the wild.

**How severe is CVE-2026-125124?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Tmatens Compose-Lint 0.31.0.

**Is there a fix for CVE-2026-125124?** Yes: fixed in 0.32.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-125124 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-125124?** Check whether you run Tmatens Compose-Lint at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 0.32.0

## Technical details

The vulnerability is an insufficient input sanitization flaw where Azure Pipelines ##vso[ logging-command openers are not escaped on all output paths in version 0.31.0. An attacker can place these openers in Compose values or file names, and when compose-lint outputs these unsanitized strings to a CI/CD job log, Azure Pipelines interprets and executes them as legitimate workflow commands. The flaw affects the pre-commit hook, Docker image, and text report output paths; the GitHub Action is not affected as it runs on GitHub Actions, not Azure Pipelines. This is fixed in version 0.32.0.

## Affected products

- tmatens compose-lint 0.31.0

## Timeline

- 2026-11-10: disclosed
- 2026-09-28: patched

## References

- [https://github.com/tmatens/compose-lint/commit/542e63126f795564a65c63887ea0dc558a500688](https://github.com/tmatens/compose-lint/commit/542e63126f795564a65c63887ea0dc558a500688)
- [https://github.com/tmatens/compose-lint/pull/945](https://github.com/tmatens/compose-lint/pull/945)

## Related threats

- [compose-lint GitHub Action workflow command injection via symlink path](https://junglewise.ai/threats/cve-2026-125125-compose-lint-is-a-docker-compose-security-linter-that-identifies)
- [compose-lint command injection via unsanitized stderr output](https://junglewise.ai/threats/cve-2026-125123-compose-lint-is-a-docker-compose-security-linter-that-identifies)
- [compose-lint CI command injection in JSON and SARIF output](https://junglewise.ai/threats/cve-2026-125122-compose-lint-is-a-docker-compose-security-linter-that-identifies)
- [compose-lint workflow command injection via Unicode whitespace](https://junglewise.ai/threats/cve-2026-125121-compose-lint-is-a-docker-compose-security-linter-that-identifies)
- [compose-lint information disclosure via incomplete .env remediation at finding limit](https://junglewise.ai/threats/cve-2026-123796-compose-lint-is-a-docker-compose-security-linter-that-identifies)