CVE-2026-123371
compose-lint is a Docker Compose security linter that identifies …
compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. From 0.2.0 until 0.32.0, compose-lint automatically follows a .compose-lint.yml policy-file symbolic link outside the project and includes part of the target line when that external file fails YAML parsing. A pull request can point the policy file at a runner credential file, causing about 30 characters around an attacker-uncontrolled parse position to appear in standard error, JSON errors, and SARIF tool execution notifications uploaded by the GitHub Action. The run exits with an error and the attacker cannot select the exact disclosed line, but public logs or Code Scanning output can reveal part of the target. This issue is fixed in version 0.32.0.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/tmatens/compose-lint/commit/e80547d33b2114040c4bc0e34ef210aee51f5058
- github.com/tmatens/compose-lint/pull/943
- github.com/tmatens/compose-lint/releases/tag/v0.32.0
- github.com/tmatens/compose-lint/security/advisories/GHSA-88f4-frh5-gmcr
- nvd.nist.gov/vuln/detail/CVE-2026-123371
- github.com/advisories/GHSA-88f4-frh5-gmcr
- nvd.nist.gov/vuln/detail/CVE-2026-123371
- cve.org/CVERecord?id=CVE-2026-123371
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.