# CVE-2026-125125: compose-lint: Workflow command injection through SARIF-directory errors triggered by pull request symlinks


- **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-xcf7-88g6-7xr8

## What is CVE-2026-125125?

CVE-2026-125125 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. From version 0.30.0 until 0.32.0, the compose-lint GitHub Action prints the resolved directory from a failed sarif-file subdirectory creation without effective command suppression. Version 0.30.0 has no stop-commands window, while version 0.31.0 prints this error outside its stop-commands window. A pull request can place a committed symlink on that path to a directory whose name contains a newline followed by a workflow command, causing the SARIF-directory error to issue commands in the job log. Only the Action with sarif-file pointing into a subdirectory is affected; a workspace-root SARIF file, the compose-lint package, the pre-commit hook, and the Docker image do not expose this message. 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-125125?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tmatens/compose-lint` | GitHub Actions | From 0.30.0 | 0.32.0 |

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

Upgrade tmatens/compose-lint to 0.32.0 or later.

## Is CVE-2026-125125 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- tmatens/compose-lint (GitHub Actions): affected from 0.30.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-125125/ (Markdown: https://insights.sbomify.com/CVE-2026-125125/index.md)
```

## Sources

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

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