# CVE-2026-125123: compose-lint: File paths embedded in pull requests can inject CI workflow commands through command-line error messages


- **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:** Yes
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-8v59-qmwv-4p6q

## What is CVE-2026-125123?

CVE-2026-125123 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's argument parser writes rejected repository paths to stderr without the output sanitizer when a path is passed without a preceding -- separator. A pull request can supply a path containing workflow-command syntax; a carriage return can position that command at the start of a new line recognized by the GitHub Actions runner, allowing the package, Docker image, or a pre-commit hook with misconfigured args to issue the command in the job log. The default pre-commit configuration includes -- and is not affected, the GitHub Action is not affected, and the lint pass or fail result is unchanged. 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-125123?

1 open source package ship an affected version, including compose-lint.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `compose-lint` | PyPI | From 0.31.0 | 0.32.0 |

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

Upgrade compose-lint to 0.32.0 or later.

## Is CVE-2026-125123 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- compose-lint (PyPI): affected from 0.31.0; fixed in 0.32.0

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-125123/ (Markdown: https://insights.sbomify.com/CVE-2026-125123/index.md)
```

## Sources

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

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