GHSA-6f4g-xm8v-pgv6: compose-lint: Compose file text can issue GitHub Actions workflow commands through the compose-lint Action

Published Nov 9, 2026
·
Updated

compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. Prior to 0.31.0, compose-lint prints attacker-controlled service names, environment keys, file lines, and other Compose text without neutralizing GitHub Actions and Azure Pipelines workflow-command openers. When a workflow processes a pull request, legacy ##[ commands or a line-leading double-colon command can create false annotations, hide log regions, mask selected strings, or invoke other commands recognized by the runner. The affected text report paths do not alter the compose-lint exit code or pass or fail result, but they can misrepresent the CI output presented to reviewers. This issue is fixed in version 0.31.0.

Affected Software

1 affected component
compose-lint<0.31.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade compose-lint to a version that resolves this vulnerability.

    Fixed in 0.31.0

Event History

Nov 9, 2026
CVE Published
via OSV·05:32 PM
Data Sourced
via OSV·05:32 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which CI workflows are exposed to this issue?

Workflows that run the compose-lint Action on pull-request-controlled Compose content are exposed if they use a compose-lint version earlier than 0.31.0. The risk is to the integrity of runner-recognized log output shown to reviewers.

2

What must an attacker control to exploit it?

An attacker needs to cause compose-lint to print crafted Compose text, such as service names, environment keys, or file lines, containing GitHub Actions or Azure Pipelines workflow-command openers. User interaction is required because a workflow must process the attacker-controlled pull request content.

3

Can this change whether the CI check passes or fails?

No. The affected text-reporting paths do not change compose-lint's exit code or its pass/fail result, but they can create misleading annotations, conceal log regions, mask selected strings, or trigger other runner-recognized commands.

4

What is the remediation?

Upgrade compose-lint to version 0.31.0, which fixes the workflow-command neutralization issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203