compose-lint: A `.compose-lint.yml` symlinked outside the project is read, and a parse error quotes part of the target
Affects compose-lintSource GCVE Database
Not known to be exploited · CVSS 2.3 Low : upgrade to 0.32.0 when convenient.
Data as of 10 Nov 2026, 17:47 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 2.3 |
|---|
- Patch
- Available – fixed in 0.32.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade compose-lint and tmatens/compose-lint to 0.32.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIcompose-lint | Affected
| Fixed in
|
| GitHubtmatens/compose-lint | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in compose-lint version 0.32.0 and later. Users should upgrade to 0.32.0 or newer to prevent reading symlinked .compose-lint.yml files outside the project directory and to suppress quoting of parse error lines. Alternatively, running compose-lint with an explicit --config option pointing to a policy file inside the project directory avoids automatic lookup and mitigates the issue. Additionally, avoid running compose-lint on untrusted pull requests on machines where files outside the checkout contain sensitive credentials.
Description
compose-lint versions from 0.2.0 up to but not including 0.32.0 automatically read a .compose-lint.yml policy file beside the Compose file. If this file is a symlink pointing outside the project directory, compose-lint follows it and reads the target file. When the target file contains invalid YAML, the parse error message includes a quoted snippet of the target file's content, exposing about 30 characters around the error line. This can leak small fragments of sensitive data, such as credentials, to pull request authors via job logs and code scanning uploads. The issue is fixed in version 0.32.0, which refuses to read symlinked policy files resolving outside the working directory and no longer quotes parse error lines.
References
- github.com/tmatens/compose-lint/security/advisories/GHSA-88f4-frh5-gmcr (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-123371 (opens in a new tab)
- github.com/tmatens/compose-lint/pull/943 (opens in a new tab)
- github.com/tmatens/compose-lint/commit/e80547d33b2114040c4bc0e34ef210aee51f5058 (opens in a new tab)
- github.com/tmatens/compose-lint (opens in a new tab)
- github.com/tmatens/compose-lint/releases/tag/v0.32.0 (opens in a new tab)