compose-lint: A pull request can make compose-lint quote a secret from a CI-generated .env into its findings
CVE-2026-123372GHSA-jf3h-8jvx-vcrg
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (compose-lint 0.32.0; tmatens/compose-lint 0.32.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI compose-lint
- Affected
- >= 0.22.0, < 0.32.0
- Fixed in
- 0.32.0
GitHub Actions tmatens/compose-lint
- Affected
- >= 0.22.0, < 0.32.0
- Fixed in
- 0.32.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-jf3h-8jvx-vcrg lists affected ranges: PyPI compose-lint >=0.22.0 =0.22.0 <=0.31.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-jf3h-8jvx-vcrg lists affected ranges: PyPI compose-lint >=0.22.0 =0.22.0 <0.32.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 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 · score source
- EPSS
- CVE-2026-123372: 0.38% estimated exploitation activity in the next 30 days; percentile 32.35 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact Since 0.22.0, compose-lint fills in `${VAR}` references from the `.env` beside the Compose file, as Compose does. The documentation says values under `environment:` are never resolved from a `.env`, "that is where secrets live". But `image:` values are resolved, and CL-0004 and CL-0019 quote the resolved image in their message and fix text. Some CI workflows write secrets into that `.env` before linting or building. In such a workflow, a pull request that changes one line to `image: "${DB_PASSWORD}"`, or `image: "nginx:${DB_PASSWORD}"`, gets the secret's value quoted in a finding. The finding reaches the job log, JSON output, and the SARIF uploaded to Code Scanning. GitHub masks registered secrets in the job log, but not in uploaded JSON or SARIF artifacts or in Code Scanning alert text. The pass/fail result is not affected. This needs a workflow that writes secrets into the `.env` beside the Compose file *and* runs on pull requests from authors who should not see them.…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-jf3h-8jvx-vcrg
- Revision 1 · created ·
Published from ghsa record GHSA-jf3h-8jvx-vcrg
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-123372 Advisory: compose-lint: A pull request can make compose-lint quote a secret from a CI-generated `.env` into its findings IDs: CVE-2026-123372, GHSA-jf3h-8jvx-vcrg Record: https://patchnext.com/advisories/cve-2026-123372 (revision 2, source checked 11 Nov 2026, 07:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 2.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: compose-lint 0.32.0; tmatens/compose-lint 0.32.0. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI compose-lint: affected >= 0.22.0, < 0.32.0; fixed in 0.32.0 - GitHub Actions tmatens/compose-lint: affected >= 0.22.0, < 0.32.0; fixed in 0.32.0 ## Suggested inspection (read-only) - `python -m pip show compose-lint`: prints the installed version. Run with the environment that serves production active. - GitHub Actions tmatens/compose-lint: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on compose-lint, tmatens/compose-lint. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-jf3h-8jvx-vcrg (GitHub-reviewed advisory GHSA-jf3h-8jvx-vcrg lists affected ranges: PyPI compose-lint >=0.22.0 =0.22.0 <=0.31.0) - Verified: https://osv.dev/vulnerability/GHSA-jf3h-8jvx-vcrg (OSV record GHSA-jf3h-8jvx-vcrg lists affected ranges: PyPI compose-lint >=0.22.0 =0.22.0 <0.32.0 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…