compose-lint: Incomplete fix for GHSA-jf3h-8jvx-vcrg: a run stopped at the finding limit quotes a secret from a
Affects compose-lintSource GCVE Database
Not known to be exploited · CVSS 2.3 Low : upgrade to 0.33.0 when convenient.
Data as of 10 Nov 2026, 17:37 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 2.3 |
|---|
- Patch
- Available – fixed in 0.33.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.33.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 fixed release (compose-lint 0.33.0) is available and should be applied to remediate this issue. Until then, workarounds include running compose-lint with the --no-env option to skip loading the sibling .env file or avoiding writing secrets into the .env file beside the Compose file in jobs that lint untrusted pull requests.
Description
compose-lint version 0.32.0 contains an incomplete fix for a previous secret exposure vulnerability (GHSA-jf3h-8jvx-vcrg). When a run exceeds 20,000 findings, the process stops before masking secret values, causing secrets from a sibling .env file to be exposed in output formats including text logs, JSON, and SARIF reports. This can occur in CI workflows that write secrets into the .env file beside the Compose file and lint pull requests from untrusted authors. No fixed release was available at the time of disclosure, but version 0.33.0 addresses this issue.
References
- github.com/tmatens/compose-lint/security/advisories/GHSA-rm8w-w798-g545 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-123796 (opens in a new tab)
- github.com/tmatens/compose-lint/pull/978 (opens in a new tab)
- github.com/tmatens/compose-lint/commit/31ec460399e06e98aa0d1cc578368a1960a8a0b3 (opens in a new tab)
- github.com/tmatens/compose-lint (opens in a new tab)
- github.com/tmatens/compose-lint/releases/tag/v0.33.0 (opens in a new tab)