compose-lint: A pull request can make compose-lint quote a secret from a CI-generated `.env` into its findings
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
Upgrade compose-lint to version 0.32.0 or later, where the issue is fixed by quoting variable references instead of resolved secret values in outputs. Alternatively, run compose-lint with the --no-env option to skip loading the sibling .env file. Avoid writing secrets into the .env file beside the Compose file in CI jobs that lint untrusted pull requests. These mitigations prevent secret values from being included in compose-lint findings and reports.
Description
compose-lint versions 0.22.0 through 0.31.0 can inadvertently disclose secret values from a CI-generated .env file when those secrets are referenced in the image field of a Docker Compose file. This occurs because compose-lint resolves ${VAR} references from the .env file and includes the resolved values in its findings, logs, JSON output, and SARIF reports. Although GitHub masks secrets in job logs, it does not mask them in uploaded JSON or SARIF artifacts or Code Scanning alert text, potentially exposing secrets in pull request workflows that have access to the .env file. The issue is fixed in version 0.32.0, which quotes the variable reference instead of the resolved secret value in outputs.
References
- github.com/tmatens/compose-lint/security/advisories/GHSA-jf3h-8jvx-vcrg (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-123372 (opens in a new tab)
- github.com/tmatens/compose-lint/pull/944 (opens in a new tab)
- github.com/tmatens/compose-lint/commit/977da9724789264c2662afe47f79220e915442c2 (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)