compose-lint: A committed symlink makes compose-lint quote a file from outside the project into its output
Affects compose-lintSource GCVE Database
Not known to be exploited · CVSS 2.3 Low : upgrade to 0.25.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.25.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.25.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.25.0 or later, where the issue is fixed. For older versions, avoid running compose-lint on untrusted pull requests on machines with sensitive files outside the checkout. Using the '--no-env' option can mitigate some exposure routes but does not fully prevent the issue. Later versions (0.32.0+) further restrict symlink following for Compose files outside the checkout. Review related advisories GHSA-6wcv-rj3c-mhv3 and GHSA-88f4-frh5-gmcr for sibling issues.
Description
compose-lint versions prior to 0.25.0 follow symlinks when reading project files, potentially exposing contents of files outside the project in its output. This can occur when a pull request commits a symlink pointing to sensitive files on the CI runner. The exposure includes quoted lines from non-YAML files and key names from env_file targets, visible in job logs and code scanning outputs. The issue is fixed starting from version 0.25.0, which restricts symlink resolution outside the project and removes quoted source lines from parse errors.
References
- github.com/tmatens/compose-lint/security/advisories/GHSA-whr6-fgpq-fpv9 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-123373 (opens in a new tab)
- github.com/tmatens/compose-lint/pull/721 (opens in a new tab)
- github.com/tmatens/compose-lint/commit/364814329417dbbc34d1ad2f3981f8a7a023799e (opens in a new tab)
- github.com/tmatens/compose-lint (opens in a new tab)
- github.com/tmatens/compose-lint/releases/tag/v0.25.0 (opens in a new tab)