CVE-2026-123796
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.32.0 until 0.33.0, compose-lint's incomplete remediation for .env secret disclosure checks the 20,000-finding limit before replacing resolved values with their variable references. A pull request can combine a secret-referencing image field with aliased content that produces more than 20,000 findings, causing the early-stop path to emit already graded findings with the resolved secret value in text, JSON, SARIF, and Code Scanning output. Exploitation requires a workflow that writes secrets into the sibling .env and lints untrusted changes, and the run exits 2 unless --allow-partial-coverage is used. This issue is fixed in version 0.33.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/31ec460399e06e98aa0d1cc578368a1960a8a0b3
- github.com/tmatens/compose-lint/pull/978
- github.com/tmatens/compose-lint/releases/tag/v0.33.0
- github.com/tmatens/compose-lint/security/advisories/GHSA-rm8w-w798-g545
- nvd.nist.gov/vuln/detail/CVE-2026-123796
- github.com/advisories/GHSA-rm8w-w798-g545
- nvd.nist.gov/vuln/detail/CVE-2026-123796
- cve.org/CVERecord?id=CVE-2026-123796
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.