compose-lint: Text in a pull request can issue CI workflow commands through JSON and SARIF output on stdout
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. --format json and --format sarif output never passed through that fix, so ##[ inside a service name or other value reaches the log intact when the output is printed to stdout rather than written to a file. The runner acts on ##[ in the middle of a line, so the JSON layout does not prevent it.
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 print JSON or SARIF output to a CI log from the compose-lint package, the pre-commit hook or the Docker image. Writing that output to a file, which SARIF upload requires, is not affected. The GitHub Action turns command processing off around each compose-lint run, so it is not affected.
Found during an internal pre-1.0 security review. It was first published as part of GHSA-r7j4-crjv-h467, together with four other gaps in the same fix. Each gap now has its own advisory.
Docker image. composelint/compose-lint tag 0.31.0 and the matching minor tag are affected, as was latest while it pointed to 0.31.0.
Releases before 0.31.0 are covered by GHSA-6f4g-xm8v-pgv6.
Patches
Fixed in 0.32.0. JSON and SARIF on stdout escape ##[ inside strings as \u005b, which decodes to the same data.
Workarounds
- Upgrade to 0.32.0 or later.
- Write
--format jsonand--format sarifoutput to a file rather than the log. - On GitHub Actions, use the
tmatens/compose-lintAction, or bracket the compose-lint step with::stop-commands::<random token>and::<token>::, as the Action does.
Reproduction
On compose-lint 0.31.0 on a GitHub-hosted runner (runner 2.337.0), a service named a##[warning]X, linted with --format json or --format sarif to stdout, creates annotations. The same file linted with the text report creates none. The composelint/compose-lint:0.31.0 image produces byte-identical output to the package.
Betroffene Software
Klicken Sie auf eine Technologie, um alle zugehörigen Schwachstellen anzuzeigen.
| Plattform | Paket | Anfällige Versionen | Behoben in |
|---|---|---|---|
| Python (PyPI) | compose-lint | >= 0.31.0, < 0.32.0 | 0.32.0 |
Verweise
- https://github.com/tmatens/compose-lint/security/advisories/GHSA-hr4h-4c45-v4q4
- https://nvd.nist.gov/vuln/detail/CVE-2026-125122
- https://github.com/tmatens/compose-lint/pull/945
- https://github.com/tmatens/compose-lint/commit/542e63126f795564a65c63887ea0dc558a500688
- https://github.com/tmatens/compose-lint
- https://github.com/tmatens/compose-lint/releases/tag/v0.32.0
- CVSS-Vektor
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- Schwäche (CWE)
CWE-117, CWE-150- Plattform
- Python (PyPI)
- Paket
compose-lint- Veröffentlicht
- 10.11.2026
- Aktualisiert
- 11.11.2026 00:17
Quellen und Lizenzen
OSV / GitHub Advisory Database - GHSA-hr4h-4c45-v4q4 - CC BY 4.0
Schwachstellenhistorie: compose-lint
Alle veröffentlichten Schwachstellen dieses Pakets (Python (PyPI)), neueste zuerst. Zeigt, ob es ein einmaliger Ausrutscher ist oder ein Paket, das man im Auge behalten muss.
- Einträge insgesamt
- 10
- Erste → letzte
- 11.2026 11.2026
- Ohne Fix
- 0
- In Angriffen ausgenutzt
- 0
Verteilung nach Schweregrad
- Mittel 3
- Niedrig 7
Veröffentlichungen pro Jahr
- 2026: 10
-
compose-lint: Text in a pull request can issue CI workflow commands through JSON and SARIF output on stdout dieser Eintrag
Erkennen Sie Schwachstellen in Ihrer Anwendung
Mit der DockRay-Integration und aktivierter Softwareinventarisierung prüft DockRay gemeldete Komponentenversionen auf bekannte Schwachstellen und benachrichtigt Sie über bestätigte Treffer. Die Abdeckung hängt von der unterstützten Technologie und den verfügbaren Meldungen ab.