# CVE-2026-123372: compose-lint: A pull request can make compose-lint quote a secret from a CI-generated `.env` into its findings


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-jf3h-8jvx-vcrg

## What is CVE-2026-123372?

CVE-2026-123372 is a low-severity vulnerability in tmatens compose-lint, published on 9 Nov 2026. 

### Official 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-123372?

2 open source packages ship an affected version, including tmatens/compose-lint and compose-lint.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tmatens/compose-lint` | GitHub Actions | From 0.22.0 | 0.32.0 |
| `compose-lint` | PyPI | From 0.22.0 | 0.32.0 |

## How do I fix CVE-2026-123372?

Upgrade tmatens/compose-lint to 0.32.0 or later.

## Is CVE-2026-123372 being exploited?

There is no known exploitation of CVE-2026-123372 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123372 and fix it if it is affected.

What it is: CVE-2026-123372 is a low-severity vulnerability in tmatens compose-lint, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123372 in the wild and no public exploit code.

Affected packages and fixed versions:
- tmatens/compose-lint (GitHub Actions): affected from 0.22.0; fixed in 0.32.0
- compose-lint (PyPI): affected from 0.22.0; fixed in 0.32.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123372/ (Markdown: https://insights.sbomify.com/CVE-2026-123372/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123372
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123372
- OSV: https://osv.dev/vulnerability/CVE-2026-123372

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123372/
Summaries are generated and may contain mistakes; the official description above is the record.