CVE-2026-123372

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

Published Nov 9, 2026 CVSS 4.0 · 2.3 Low EPSS < 1% KEV · Not listed
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-jf3h-8jvx-vcrg compose-lint: A pull request can make compose-lint quote a secret from a CI-generated `.env` into its findings
History
Type Values Removed Values Added
First Time appeared Tmatens
Tmatens compose-lint
Vendors & Products Tmatens
Tmatens compose-lint
Type Values Removed Values Added
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.
Title compose-lint: A pull request can make compose-lint quote a secret from a CI-generated `.env` into its findings
Weaknesses CWE-200
CWE-532
References
Metrics cvssV4_0

{'score': 2.3, 'vector': '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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 13, 2026, 12:29 PM
Reserved
Nov 5, 2026, 8:43 PM
Status
Deferred
Published
Nov 9, 2026, 6:17 PM
Modified
Nov 13, 2026, 1:17 PM