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

Low 2.3 Published Updated
Exploited in the wild
Not known
Fix
Available

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, CWE-200

Which versions are affected by CVE-2026-123372?

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

PackageAffectedFixed in
tmatens/compose-lint GitHub ActionsFrom 0.22.00.32.0
compose-lint PyPIFrom 0.22.00.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.

Sources

Also known as GHSA-jf3h-8jvx-vcrg.

Is CVE-2026-123372 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free