compose-lint: A pull request can make compose-lint quote a secret from a CI-generated `.env` into its findings
- 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 leak the full value of a secret from a CI-generated `.env` file into its CL-0004 and CL-0019 findings, including job logs, JSON output, SARIF artifacts, and Code Scanning alerts. An attacker can reach it remotely, without logging in, by submitting a pull request that references the secret variable, but this works only in workflows that have secrets available, such as `pull_request_target`, same-repository branches, or self-hosted runners that keep the `.env` file.
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.22.0 until 0.32.0, compose-lint substitutes values from a sibling .env file into image fields and quotes the resolved value in CL-0004 and CL-0019 finding messages and fix text. In a workflow that writes secrets into that file and then lints untrusted pull-request content, an attacker can reference a secret variable so its whole value reaches the job log, JSON output, SARIF artifacts, and Code Scanning alerts. Fork pull requests normally lack secrets, so exploitation requires a secret-bearing workflow such as pull_request_target, same-repository branches, or a retained .env on a self-hosted runner, and the pass or fail result is unchanged. 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
- Record last updated
- First seen by cve.now
Affected versions
- tmatens compose-lint
From 0.22.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-123372
Is CVE-2026-123372 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-123372?
compose-lint: from 0.22.0 before 0.32.0.Source: cve.now feed data
How do I fix CVE-2026-123372?
Upgrade to a fixed version: 0.32.0.Source: cve.now feed data