cve.bz

CVE-2026-125121 compose-lint: Text in a pull request can still issue CI workflow commands through compose-lint 0.31.0's output

5.3 mediumEPSS 0.4%Fix available

Medium (5.3) in tmatens compose-lint. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in compose-lint 0.32.0.

On this page
compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. In version 0.31.0, compose-lint escapes GitHub Actions workflow-command openers only after ASCII spaces and tabs, while the runner strips all leading Unicode whitespace before interpreting a line. Untrusted Compose values or repository paths beginning with Unicode whitespace followed by :: can therefore reach the text report, fix guidance, the fix dry-run diff, and stderr diagnostics as workflow commands when the package, pre-commit hook, or Docker image runs directly in CI. The GitHub Action is not affected because it disables command processing, and the flaw does not change the lint pass or fail result. This issue is fixed in version 0.32.0.

Severity

CVSS 4.0

5.3 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N
EPSS
0.4% estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-117 Improper Output Neutralization for Logs
CWE-150 Improper Neutralization of Escape, Meta, or Control Sequences
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-125121 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125121?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125121?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125121 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-125121

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-125121](https://cve.bz/cve/badge/CVE-2026-125121.svg)](https://cve.bz/cve/CVE-2026-125121)

HTML:

<a href="https://cve.bz/cve/CVE-2026-125121"><img src="https://cve.bz/cve/badge/CVE-2026-125121.svg" alt="CVE-2026-125121"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
tmatens compose-lint>= 0.31.0, < 0.32.0

Fix and patched versions

  • compose-lint (PyPI): fixed in 0.32.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-r7j4-crjv-h467PyPIcompose-lint>=0.31.0 <0.32.00.32.0

Attack patterns (CAPEC)

  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-93 Log Injection-Tampering-Forging Likelihood: High · Severity: High
  • CAPEC-268 Audit Log Manipulation
  • CAPEC-41 Using Meta-characters in E-mail Headers to Inject Malicious Payloads Likelihood: High · Severity: High
  • CAPEC-134 Email Injection Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON