CVE-2026-125125: compose-lint: Workflow command injection through SARIF-directory errors triggered by pull request symlinks
Impact In Action tags v0.30.0 and v0.31.0, when sarif-file: names a file in a subdirectory that can't be created, the Action prints the directory's resolved path in an error message. In v0.31.0 that message is outside the window in which the Action turns command processing off, and v0.30.0 has no such window.
Published Nov 10, 2026
Affected packages
tmatens/compose-lint
- Ecosystem
- GitHub Actions
- Affected
- >= 0.30.0, <= 0.31.0
- Fixed in
- 0.32.0
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
In Action tags v0.30.0 and v0.31.0, when sarif-file: names a file in a subdirectory that can't be created, the Action prints the directory's resolved path in an error message. In v0.31.0 that message is outside the window in which the Action turns command processing off, and v0.30.0 has no such window. A pull request can commit a symlink on that path to a directory whose name contains a newline followed by a command.
A pull request can therefore create annotations, fold or hide parts of the job log, or issue other commands the runner accepts, when CI runs compose-lint over it, before anyone reviews it. The pass/fail result is not changed.
Only the Action is affected, and only when sarif-file: points into a subdirectory. The documented setup, sarif-file: results.sarif at the repository root, is not affected. The compose-lint package, the pre-commit hook and the Docker image do not print this message.
Found during an internal pre-1.0 security review. It was first published as part of GHSA-r7j4-crjv-h467, together with four other gaps in the same fix. Each gap now has its own advisory.
Patches
Fixed in 0.32.0. The SARIF-directory error names the sarif-file: input as written.
Workarounds
- Upgrade to 0.32.0 or later.
- Keep
sarif-fileat the workspace root, for examplesarif-file: results.sarif.
Reproduction
On a GitHub-hosted runner (runner 2.337.0), the Action at v0.31.0 with sarif-file: out/reports/results.sarif, where out is a committed symlink to a directory named d\n::warning::X that contains a regular file reports, creates an annotation. With sarif-file at the repository root it creates none.
References
- https://github.com/tmatens/compose-lint/security/advisories/GHSA-xcf7-88g6-7xr8
- https://nvd.nist.gov/vuln/detail/CVE-2026-125125
- https://github.com/tmatens/compose-lint/pull/945
- https://github.com/tmatens/compose-lint/commit/542e63126f795564a65c63887ea0dc558a500688
- https://github.com/tmatens/compose-lint/releases/tag/v0.32.0
- https://github.com/advisories/GHSA-xcf7-88g6-7xr8
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More GitHub Actions vulnerabilities
All GitHub Actions entriesCVE-2026-123368
compose-lint: .env read through a symlink outside the project can expose the CI job's environment
low3.1Nov 10, 2026CVE-2026-123369
compose-lint: Compose file text can issue GitHub Actions workflow commands through the compose-lint Action
medium4.3Nov 10, 2026CVE-2026-123371
compose-lint: A `.compose-lint.yml` symlinked outside the project is read, and a parse error quotes part of the target
low2.3Nov 10, 2026CVE-2026-123372
compose-lint: A pull request can make compose-lint quote a secret from a CI-generated `.env` into its findings
low2.3Nov 10, 2026CVE-2026-123373
compose-lint: A committed symlink makes compose-lint quote a file from outside the project into its output
low2.3Nov 10, 2026CVE-2026-123796
compose-lint: Incomplete fix for GHSA-jf3h-8jvx-vcrg: a run stopped at the finding limit quotes a secret from a CI-generated `.env`
low2.3Nov 10, 2026
