compose-lint: Text in a pull request can still issue CI workflow commands through compose-lint 0.31.0's output

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N · score source

EPSS

No dated EPSS signal available.

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 everything compose-lint prints, and the 0.31.0 changelog says the report "escapes both openers (also covering Azure Pipelines)". Five paths were left open: - Unicode whitespace before a line-leading `::`. The runner strips all Unicode whitespace from the start of a line before it looks for a command. compose-lint only accounted for spaces and tabs, so a no-break space or another Unicode space ahead of `::` is not escaped. It can come from a Compose value, or from a file name: the text report's file heading and per-file summary, and the `fix` summary on stderr, start with the path as given, so a directory named with a leading no-break space followed by `::` puts a command at the start of a line. This reaches those lines, the text report's fix guidance, the `fix` dry-run diff, and continuation lines of…

Published by the source

10 Nov 2026, 18:28 UTC

Last modified by the source

11 Nov 2026, 02:57 UTC

Source last checked

11 Nov 2026, 07:05 UTC

1. Revision 2 · amended · 11 Nov 2026

   Amended from osv record GHSA-r7j4-crjv-h467

2. Revision 1 · created · 10 Nov 2026

   Published from ghsa record GHSA-r7j4-crjv-h467

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

# Patch Next advisory brief: CVE-2026-125121

Advisory: compose-lint: Text in a pull request can still issue CI workflow commands through compose-lint 0.31.0's output
IDs: CVE-2026-125121, GHSA-r7j4-crjv-h467
Record: https://patchnext.com/advisories/cve-2026-125121 (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: Medium (CVSS 5.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-r7j4-crjv-h467 (GitHub-reviewed advisory GHSA-r7j4-crjv-h467 lists affected ranges: PyPI compose-lint >=0.31.0 <0.32.0)
- Verified: https://osv.dev/vulnerability/GHSA-r7j4-crjv-h467 (OSV record GHSA-r7j4-crjv-h467 lists affected ranges: PyPI compose-lint >=0.31.0 <0.32.0 (fixed))

Commands are suggestions: review each one before running it.