Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-hr4h-4c45-v4q4 | compose-lint: Text in a pull request can issue CI workflow commands through JSON and SARIF output on stdout |
Sat, 14 Nov 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tmatens
Tmatens compose-lint |
|
| Vendors & Products |
Tmatens
Tmatens compose-lint |
Tue, 10 Nov 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. In version 0.31.0, compose-lint does not sanitize the ##[ workflow-command opener inside strings written by --format json or --format sarif to stdout. A pull request can place that opener in a service name or other Compose value, and the GitHub Actions runner recognizes it even in the middle of a serialized line when the package, pre-commit hook, or Docker image prints JSON or SARIF to the job log. Writing the output to a file and using the compose-lint GitHub Action are not affected, and the flaw does not change the lint pass or fail result. This issue is fixed in version 0.32.0. | |
| Title | compose-lint: Text in a pull request can issue CI workflow commands through compose-lint 0.31.0's JSON and SARIF output on stdout | |
| Weaknesses | CWE-117 CWE-150 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-13T15:25:23.463Z
Reserved: 2026-11-09T17:45:35.936Z
Link: CVE-2026-125122
No data.
Status : Deferred
Published: 2026-11-10T17:17:26.603
Modified: 2026-11-13T16:17:43.487
Link: CVE-2026-125122
No data.
OpenCVE Enrichment
Updated: 2026-11-15T03:45:03Z
Github GHSA