CVSS 4.0
2.3 lowCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NCVE-2026-123371
Low (2.3) in tmatens compose-lint. EPSS 0.4% 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. From 0.2.0 until 0.32.0, compose-lint automatically follows a .compose-lint.yml policy-file symbolic link outside the project and includes part of the target line when that external file fails YAML parsing. A pull request can point the policy file at a runner credential file, causing about 30 characters around an attacker-uncontrolled parse position to appear in standard error, JSON errors, and SARIF tool execution notifications uploaded by the GitHub Action. The run exits with an error and the attacker cannot select the exact disclosed line, but public logs or Code Scanning output can reveal part of the target. This issue is fixed in version 0.32.0.
Severity
- EPSS
- 0.4% estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
- CWEs
- CWE-59 Improper Link Resolution Before File Access (Link Following)
CWE-209 Generation of Error Message Containing Sensitive Information - Published
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123371 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123371?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123371?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-123371 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.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| tmatens compose-lint | >= 0.2.0, < 0.32.0 |
Attack patterns (CAPEC)
- CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
- CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
- CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
- CAPEC-132 Symlink Attack Likelihood: Low · Severity: High
- CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
- CAPEC-54 Query System for Information Likelihood: High · Severity: Low
- CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low
- CAPEC-463 Padding Oracle Crypto Attack Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.