CVSS 4.0
2.3 lowCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:NCVE-2026-125124 compose-lint: Text in a pull request can reach Azure Pipelines as logging commands through compose-lint 0.31.0's output
Low (2.3) in tmatens compose-lint. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. In version 0.31.0, compose-lint does not neutralize the Azure Pipelines ##vso[ logging-command opener on any output path. A pull request can place that opener in a Compose value or file name, allowing output from the package, pre-commit hook, or Docker image to issue logging commands when printed to an Azure Pipelines job log. The maintainer did not reproduce the behavior on an Azure Pipelines agent. The GitHub Action is not affected because it runs only on GitHub Actions, and releases before 0.31.0 are outside this advisory because they did not claim Azure Pipelines coverage. This issue is fixed in version 0.32.0.
Severity
- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 23rd 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: no · Technical impact: total, assessed 2026-11-14. 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
Show the prompt
Explain CVE-2026-125124 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125124?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125124?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-125124 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
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:
[](https://cve.bz/cve/CVE-2026-125124)
HTML:
<a href="https://cve.bz/cve/CVE-2026-125124"><img src="https://cve.bz/cve/badge/CVE-2026-125124.svg" alt="CVE-2026-125124"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| tmatens compose-lint | = 0.31.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
- The NVD deferred its analysis
Changes since this site first stored the record. The same for every record: /api/public/changes.