CVE-2026-123372
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.22.0 until 0.32.0, compose-lint substitutes values from a sibling .env file into image fields and quotes the resolved value in CL-0004 and CL-0019 finding messages and fix text. In a workflow that writes secrets into that file and then lints untrusted pull-request content, an attacker can reference a secret variable so its whole value reaches the job log, JSON output, SARIF artifacts, and Code Scanning alerts. Fork pull requests normally lack secrets, so exploitation requires a secret-bearing workflow such as pull_request_target, same-repository branches, or a retained .env on a self-hosted runner, and the pass or fail result is unchanged. 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/977da9724789264c2662afe47f79220e915442c2
- github.com/tmatens/compose-lint/pull/944
- github.com/tmatens/compose-lint/releases/tag/v0.32.0
- github.com/tmatens/compose-lint/security/advisories/GHSA-jf3h-8jvx-vcrg
- nvd.nist.gov/vuln/detail/CVE-2026-123372
- github.com/advisories/GHSA-jf3h-8jvx-vcrg
- nvd.nist.gov/vuln/detail/CVE-2026-123372
- cve.org/CVERecord?id=CVE-2026-123372
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.