CVE-2026-123368: compose-lint · .env read through a symlink outside the project can expose the CI job's environment
Affects compose-lintSource GCVE Database
Not known to be exploited · CVSS 2.3 Low : upgrade to 0.31.0 when convenient.
Data as of 10 Nov 2026, 17:48 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 2.3 |
|---|
- Patch
- Available – fixed in 0.31.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.31.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.31.0, which enforces containment checks on .env files and refuses those resolving outside the project directory. Users should upgrade to version 0.31.0 or later. As a workaround, running compose-lint with the --no-env option disables reading the sibling .env file entirely. Additionally, avoid running compose-lint on untrusted pull requests in CI jobs that have secrets in their environment.
Description
compose-lint versions from 0.22.0 up to but not including 0.31.0 improperly follow symlinks when reading the .env file, allowing a symlink outside the project directory to be read. This can expose environment variables from the CI runner, including secrets in certain configurations, via log outputs in JSON or SARIF formats. The issue is fixed in version 0.31.0 by enforcing containment checks on .env reads and refusing .env files that resolve outside the project directory.
References
- github.com/tmatens/compose-lint/security/advisories/GHSA-6wcv-rj3c-mhv3 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-123368 (opens in a new tab)
- github.com/tmatens/compose-lint/pull/917 (opens in a new tab)
- github.com/tmatens/compose-lint/commit/c43204ad4dab11d54e20574a52bc4e5835246ca5 (opens in a new tab)
- github.com/tmatens/compose-lint (opens in a new tab)
- github.com/tmatens/compose-lint/releases/tag/v0.31.0 (opens in a new tab)