CVE-2026-123373
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.25.0, compose-lint follows a project-controlled symbolic link used as the Compose file outside the project. The same issue affects compose.override.yml and a COMPOSE_FILE entry from 0.22.0, and an env_file target from 0.23.0. If an external Compose-related target fails YAML parsing, the error quotes an attacker-uncontrolled line into standard error, JSON errors, and SARIF notifications, while an external env_file can expose credential-like key names through CL-0020 and CL-0021 findings. The attacker selects the target path but not the exact parser-failure line, values from env_file are not printed, and the pass or fail result is unchanged. This issue is fixed in version 0.25.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/364814329417dbbc34d1ad2f3981f8a7a023799e
- github.com/tmatens/compose-lint/pull/721
- github.com/tmatens/compose-lint/releases/tag/v0.25.0
- github.com/tmatens/compose-lint/security/advisories/GHSA-whr6-fgpq-fpv9
- nvd.nist.gov/vuln/detail/CVE-2026-123373
- github.com/advisories/GHSA-whr6-fgpq-fpv9
- nvd.nist.gov/vuln/detail/CVE-2026-123373
- cve.org/CVERecord?id=CVE-2026-123373
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.