compose-lint: A committed symlink makes compose-lint quote a file from outside the project into its output
- Exploited
- No known exploitation
- Fix
- Fixed in 0.25.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.25.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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
compose-lint, a Docker Compose security linter, can be made to quote a line from a file outside the project into its error output, and to reveal credential-like key names from an external env_file in CL-0020 and CL-0021 findings, through a committed symbolic link. An attacker can reach this remotely, without logging in, but a user must still run the linter on the affected project.
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.25.0, compose-lint follows a project-controlled symbolic link used as the Compose file outside the project. The same issue affects compose.override.yml and a COMPOSE_FILE entry from 0.22.0, and an env_file target from 0.23.0. If an external Compose-related target fails YAML parsing, the error quotes an attacker-uncontrolled line into standard error, JSON errors, and SARIF notifications, while an external env_file can expose credential-like key names through CL-0020 and CL-0021 findings. The attacker selects the target path but not the exact parser-failure line, values from env_file are not printed, and the pass or fail result is unchanged. This issue is fixed in version 0.25.0.
cve.now Index
- Exploitation0/40No signal
- 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.25.0.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- tmatens compose-lint
From 0.2.0 · fixed in 0.25.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-123373
Is CVE-2026-123373 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-123373?
compose-lint: from 0.2.0 before 0.25.0.Source: cve.now feed data
How do I fix CVE-2026-123373?
Upgrade to a fixed version: 0.25.0.Source: cve.now feed data