CVE-2026-123373 · Package
NO FIX YET · SEE WHAT TO DO
compose-lint, a Docker Compose security linter, follows a project-controlled symbolic link to read Compose files outside the project directory. On a parse failure it can echo an external file line and expose credential-like key names from env_files in its findings.
first public Sep 28, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams that run compose-lint on Compose projects, especially on code from untrusted sources such as pull requests or third-party repositories. Exposure requires a symlink or env_file pointing outside the project, and the impact is limited to file contents echoed in linter output. Teams that only lint their own trusted projects with no external targets have a lower risk.
Not affected if trusted-repos-only, version-0.25.0-or-later
Who cares ci, compose-lint, docker-compose
compose-lint --version or the package manifest; versions from 0.2.0 through 0.24.x are affected.0.25.0compose-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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/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
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.