Summary
compose-lint: A .compose-lint.yml symlinked outside the project is read, and a parse error quotes part of the target
Workarounds
- Upgrade to 0.32.0 or later.
- Run with an explicit
--configpointing at a policy file inside the project; the automatic lookup is then skipped. - Don't run compose-lint on untrusted pull requests on a machine whose files outside the checkout hold credentials.
Reproduction
project/.compose-lint.yml -> /path/outside/project/credentials (symlink)
project/compose.yml services: {web: {image: nginx:1.27}}
compose-lint --format sarif compose.yml exits 2, and the notification text quotes the start of the target's second line.
Impact
compose-lint automatically reads a .compose-lint.yml policy file beside the Compose file. It is meant to read nothing outside the project directory, but it follows that file if it is a symlink, wherever it points.
A pull request can commit .compose-lint.yml as a symlink to a file on the CI runner. If the target is not valid YAML, the error compose-lint reports quotes part of the line the parser failed on. That quote reaches the job log (standard error), JSON errors[], and the SARIF toolExecutionNotifications, which the Action uploads to Code Scanning. The run exits 2.
What can be read is small. The quote is cut to about 30 characters around the error position, and the attacker cannot choose which line of the target the parser fails on. For an INI-style credentials file, this was the start of the second line (aws_access_key_id = followed by the first characters of the value). Targets in KEY=value form, and YAML files that parse, disclosed no values in testing. The pass/fail result is not affected. On a public repository, the job log is visible to the pull request's author.
The Compose file loader stopped quoting source lines in parse errors in 0.25.0 (GHSA-whr6-fgpq-fpv9). The policy loader did not.
Found during an internal pre-1.0 security review.
GitHub Action. Action tags v0.18.0 through v0.31.0 install their own compose-lint version and are affected. Earlier tags install the newest release unless version: is set, and so currently install an affected one.
Docker image. composelint/compose-lint tags 0.3.3 through 0.31.0, the matching minor tags, and latest are affected. Inside the container, a symlink resolves within the container, so what can be read is the container's own files and anything mounted into it.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Fixed in 0.32.0. A .compose-lint.yml discovered in the working directory that resolves outside it is refused with exit 2 rather than read, and a policy parse error no longer quotes the line it failed on, matching the Compose loader. --config is read as given. 0.32.0 also stops following a Compose file that is a symlink to a target outside the checkout.
Frequently Asked Questions
- What is CVE-2026-123371? CVE-2026-123371 is a low-severity security vulnerability in compose-lint (pip), affecting versions >= 0.2.0, <= 0.31.0. It is fixed in 0.32.0.
- Which packages are affected by CVE-2026-123371?
compose-lint(pip) (versions >= 0.2.0, <= 0.31.0)tmatens/compose-lint(actions) (versions >= 0.2.0, <= 0.31.0)
- Is there a fix for CVE-2026-123371? Yes. CVE-2026-123371 is fixed in 0.32.0. Upgrade to this version or later.
- Is CVE-2026-123371 exploitable, and should I be worried? Whether CVE-2026-123371 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-123371 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-123371?
- Upgrade
compose-lintto 0.32.0 or later - Upgrade
tmatens/compose-lintto 0.32.0 or later
- Upgrade