# CVE-2026-125124: compose-lint: Text in a pull request can reach Azure Pipelines as logging commands through compose-lint 0.31.0's output


- **Severity:** Low 2.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-m4xg-839g-24cv

## What is CVE-2026-125124?

CVE-2026-125124 is a low-severity vulnerability in tmatens compose-lint, published on 10 Nov 2026. 

### Official description

compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. In version 0.31.0, compose-lint does not neutralize the Azure Pipelines ##vso[ logging-command opener on any output path. A pull request can place that opener in a Compose value or file name, allowing output from the package, pre-commit hook, or Docker image to issue logging commands when printed to an Azure Pipelines job log. The maintainer did not reproduce the behavior on an Azure Pipelines agent. The GitHub Action is not affected because it runs only on GitHub Actions, and releases before 0.31.0 are outside this advisory because they did not claim Azure Pipelines coverage. This issue is fixed in version 0.32.0.

Weakness: CWE-150 (Improper Neutralization of Escape, Meta, or Control Sequences), CWE-117 (Improper Output Neutralization for Logs)

## Which versions are affected by CVE-2026-125124?


## How do I fix CVE-2026-125124?

No fix has been published for CVE-2026-125124 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-125124 being exploited?

There is no known exploitation of CVE-2026-125124 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125124 and fix it if it is affected.

What it is: CVE-2026-125124 is a low-severity vulnerability in tmatens compose-lint, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125124 in the wild and no public exploit code.

Affected product: tmatens compose-lint. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125124/ (Markdown: https://insights.sbomify.com/CVE-2026-125124/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125124
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125124
- OSV: https://osv.dev/vulnerability/CVE-2026-125124

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125124/
Summaries are generated and may contain mistakes; the official description above is the record.