CVE-2026-123369

CVE-2026-123369 is a medium-severity security vulnerability in tmatens/compose-lint (actions), affecting versions >= 0.2.0, <= 0.30.0. It is fixed in 0.31.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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

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

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.

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.

CVE-2026-123369 has a CVSS score of 4.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.31.0); upgrading removes the vulnerable code path.

Affected versions

tmatens/compose-lint (>= 0.2.0, <= 0.30.0) compose-lint (<= 0.30.0)

Security releases

tmatens/compose-lint → 0.31.0 (actions) compose-lint → 0.31.0 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

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.

Frequently Asked Questions

  1. What is CVE-2026-123369? CVE-2026-123369 is a medium-severity security vulnerability in tmatens/compose-lint (actions), affecting versions >= 0.2.0, <= 0.30.0. It is fixed in 0.31.0.
  2. How severe is CVE-2026-123369? CVE-2026-123369 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by CVE-2026-123369?
    • tmatens/compose-lint (actions) (versions >= 0.2.0, <= 0.30.0)
    • compose-lint (pip) (versions <= 0.30.0)
  4. Is there a fix for CVE-2026-123369? Yes. CVE-2026-123369 is fixed in 0.31.0. Upgrade to this version or later.
  5. Is CVE-2026-123369 exploitable, and should I be worried? Whether CVE-2026-123369 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-123369 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-123369?
    • Upgrade tmatens/compose-lint to 0.31.0 or later
    • Upgrade compose-lint to 0.31.0 or later

Other vulnerabilities in tmatens/compose-lint

Stop the waste.
Protect your environment with Kodem.