Medium

compose-lint: Compose file text can issue GitHub Actions workflow commands through the compose-lint Action

  • Disclosed: 10.11.2026
  • Updated: 10.11.2026 18:17

Impact

The GitHub Actions runner treats certain text in a step's output as commands. The legacy form, ##[command], is recognized anywhere in a line. compose-lint's text report prints service names, environment keys and lines of the Compose file, and it does not neutralize ##[. Inside the compose-lint Action, a Compose file from a pull request can therefore:

  • create fake error or warning annotations on the pull request (##[error], ##[warning])
  • fold the rest of the log, including the real verdict, out of sight (##[group])
  • blank out chosen strings for the rest of the log (##[add-mask])

GitHub has postponed removing the deprecated set-output log command, so the runner still honors it. A test run of the Action on a GitHub-hosted runner confirmed that a ::set-output line from a Compose file is processed. Whether it can override the Action's own sarif-written output, which decides whether the SARIF upload step runs, has not been tested.

The exit code and the pass/fail result are not affected. Azure Pipelines parses the same ##[ syntax, so the pip package is listed for anyone printing the text report in other CI systems.

Found during an internal pre-1.0 security review.

Patches

Fixed in 0.31.0. The Action stops the runner from processing workflow commands while compose-lint's output is printed, using a random stop-commands token. The text report also escapes ##[, and :: at the start of a line, in anything taken from the Compose file.

Workarounds

  • In your own workflow, wrap the compose-lint step in ::stop-commands::<random token> and ::<random token>::.
  • Use --format json or --format sarif rather than the text report when linting untrusted pull requests.

Reproduction

yaml
services:
  web:
    image: "nginx:1.25"
    environment:
      "##[error]DB_PASSWORD": placeholder
  "##[group]svc":
    image: "nginx:1.25"
    privileged: true

Run through the Action, this produces a fake error annotation and folds the remaining log lines, including the FAIL verdict, into a collapsed group.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) compose-lint < 0.31.0 0.31.0

References

CVSS score 4.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Weakness (CWE)
CWE-117, CWE-150
Platform
Python (PyPI)
Package
compose-lint
Disclosed
10.11.2026
Updated
10.11.2026 18:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-6f4g-xm8v-pgv6 - CC BY 4.0

Vulnerability history: compose-lint

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (10) in the archive
Total entries
10
First → latest
11.2026 11.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Medium 3
  • Low 7

Disclosures per year

  1. 2026: 10
Severity:
  1. compose-lint: Compose file text can issue GitHub Actions workflow commands through the compose-lint Action this entry
    Medium · 4.3 CVE-2026-123369 < 0.31.0 0.31.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.