CVE-2026-125125 json
compose-lint: A symlink in a pull request can issue workflow commands through the compose-lint Action's SARIF-directory error message
published yesterday modified yesterday also EUVD-2026-121405 , GHSA-xcf7-88g6-7xr8
- cvss
- 2.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- github-actions tmatens/compose-lint 0.32.0
Is CVE-2026-125125 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 4.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| github-actions | tmatens/compose-lint | >=0.30.0, <0.32.0 |
0.32.0 |
Affected products
- tmatens compose-lint
Classification
References
-
github.com
/tmatens/compose-lint/pull/945
web
-
github.com
/tmatens/compose-lint/commit/542e63126f795564a65c63887ea0dc558a500688
web
-
github.com
/tmatens/compose-lint/security/advisories/GHSA-xcf7-88g6-7xr8
web
-
github.com
/tmatens/compose-lint/releases/tag/v0.32.0
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-125125
advisory
-
github.com
/tmatens/compose-lint
package
Sources
- CVE List CVE-2026-125125
- GitHub Advisory GHSA-xcf7-88g6-7xr8
- NVD CVE-2026-125125
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.