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