compose-lint: A `.compose-lint.yml` symlinked outside the project is read, and a parse error quotes part of the target
- Exploited
- No known exploitation
- Fix
- Fixed in 0.32.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.32.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
compose-lint, a Docker Compose security linter, can be made to read part of a file outside the project, such as a runner credential file, by remote attackers without logging in, using a symbolic link in its `.compose-lint.yml` policy file. When that external file fails YAML parsing, about 30 characters of it appear in standard error, JSON errors, and SARIF output uploaded by the GitHub Action, though the attacker cannot choose which part is shown.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. From 0.2.0 until 0.32.0, compose-lint automatically follows a .compose-lint.yml policy-file symbolic link outside the project and includes part of the target line when that external file fails YAML parsing. A pull request can point the policy file at a runner credential file, causing about 30 characters around an attacker-uncontrolled parse position to appear in standard error, JSON errors, and SARIF tool execution notifications uploaded by the GitHub Action. The run exits with an error and the attacker cannot select the exact disclosed line, but public logs or Code Scanning output can reveal part of the target. This issue is fixed in version 0.32.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.32.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- tmatens compose-lint
From 0.2.0 · fixed in 0.32.0
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123371
Is CVE-2026-123371 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-123371?
compose-lint: from 0.2.0 before 0.32.0.Source: cve.now feed data
How do I fix CVE-2026-123371?
Upgrade to a fixed version: 0.32.0.Source: cve.now feed data