Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.3amended

compose-lint: File paths embedded in pull requests can inject CI workflow commands through command-line error messages

CVE-2026-125123GHSA-8v59-qmwv-4p6q

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (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.

Add to your agent

Affected packages

Sources

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:N/VI:L/VA:N/SC:N/SI:L/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact 0.31.0 fixed GHSA-6f4g-xm8v-pgv6, where text from a Compose file became GitHub Actions workflow commands in compose-lint's output. The fix escapes the command openers in compose-lint's own output, but not in the argument parser's error messages. When a repository path reaches compose-lint's arguments without a `--` before it, the argument parser prints it raw in its error message. That includes a carriage return, which the runner treats as a line break, so a command can also start a new line there. A pull request can therefore create annotations, fold or hide parts of the job log, or issue other commands the runner accepts, when CI runs compose-lint over it, before anyone reviews it. The pass/fail result is not changed. Affected setups pass repository paths to compose-lint without a `--` before them: the pre-commit hook when `args:` is set without the documented trailing `--`, or the `compose-lint` package or Docker image called that way in a workflow. The pre-commit…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-8v59-qmwv-4p6q

  2. Revision 1 · created ·

    Published from ghsa record GHSA-8v59-qmwv-4p6q

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-125123

Advisory: compose-lint: File paths embedded in pull requests can inject CI workflow commands through command-line error messages
IDs: CVE-2026-125123, GHSA-8v59-qmwv-4p6q
Record: https://patchnext.com/advisories/cve-2026-125123 (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. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI compose-lint: affected >= 0.31.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.

## 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.
- 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-8v59-qmwv-4p6q (GitHub-reviewed advisory GHSA-8v59-qmwv-4p6q lists affected ranges: PyPI compose-lint >=0.31.0 <=0.31.0)
- Verified: https://osv.dev/vulnerability/GHSA-8v59-qmwv-4p6q (OSV record GHSA-8v59-qmwv-4p6q lists affected ranges: PyPI compose-lint >=0.31.0 <0.32.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…