compose-lint: Incomplete fix for GHSA-jf3h-8jvx-vcrg: a run stopped at the finding limit quotes a secret from a CI-generated .env

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-123796: 0.30% estimated exploitation activity in the next 30 days; percentile 23.38 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact This is an incomplete fix for GHSA-jf3h-8jvx-vcrg. 0.32.0 made findings quote the `${NAME}` a sibling `.env` filled in, instead of its value. The same release added a stop at 20,000 findings per document, and that stop is checked before the quoting step. A run that hits it reports the findings graded so far with the resolved values still in them, in text, JSON and SARIF output. That happens with or without `--allow-partial-coverage`. The attack is the one GHSA-jf3h-8jvx-vcrg describes. In a CI workflow that writes secrets into the `.env` beside the Compose file, a pull request changes a line to `image: "${DB_PASSWORD}"`. It also pushes the document past 20,000 findings, which a few hundred lines can do, because an aliased list is graded once for each service that uses it. The secret's value is quoted in a finding that reaches the job log, the JSON output and the SARIF uploaded to Code Scanning. GitHub masks registered secrets in the job log, but not in uploaded JSON or…

Published by the source

10 Nov 2026, 15:57 UTC

Last modified by the source

10 Nov 2026, 16:15 UTC

Source last checked

11 Nov 2026, 07:05 UTC

1. Revision 2 · amended · 11 Nov 2026

   Amended from osv record GHSA-rm8w-w798-g545

2. Revision 1 · created · 10 Nov 2026

   Published from ghsa record GHSA-rm8w-w798-g545

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-123796

Advisory: compose-lint: Incomplete fix for GHSA-jf3h-8jvx-vcrg: a run stopped at the finding limit quotes a secret from a CI-generated `.env`
IDs: CVE-2026-123796, GHSA-rm8w-w798-g545
Record: https://patchnext.com/advisories/cve-2026-123796 (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.33.0; tmatens/compose-lint 0.33.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI compose-lint: affected >= 0.32.0, < 0.33.0; fixed in 0.33.0
- GitHub Actions tmatens/compose-lint: affected >= 0.32.0, < 0.33.0; fixed in 0.33.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-rm8w-w798-g545 (GitHub-reviewed advisory GHSA-rm8w-w798-g545 lists affected ranges: PyPI compose-lint >=0.32.0 =0.32.0 <=0.32.0)
- Verified: https://osv.dev/vulnerability/GHSA-rm8w-w798-g545 (OSV record GHSA-rm8w-w798-g545 lists affected ranges: PyPI compose-lint >=0.32.0 =0.32.0 <0.33.0 (fixed))

Commands are suggestions: review each one before running it.