# CVE-2026-123371: compose-lint: A `.compose-lint.yml` symlinked outside the project is read, and a parse error quotes part of the target


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-88f4-frh5-gmcr

## What is CVE-2026-123371?

CVE-2026-123371 is a low-severity vulnerability in tmatens compose-lint, published on 9 Nov 2026. 

### Official description

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.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2026-123371?

2 open source packages ship an affected version, including tmatens/compose-lint and compose-lint.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tmatens/compose-lint` | GitHub Actions | From 0.2.0 | 0.32.0 |
| `compose-lint` | PyPI | From 0.2.0 | 0.32.0 |

## How do I fix CVE-2026-123371?

Upgrade tmatens/compose-lint to 0.32.0 or later.

## Is CVE-2026-123371 being exploited?

There is no known exploitation of CVE-2026-123371 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123371 and fix it if it is affected.

What it is: CVE-2026-123371 is a low-severity vulnerability in tmatens compose-lint, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123371 in the wild and no public exploit code.

Affected packages and fixed versions:
- tmatens/compose-lint (GitHub Actions): affected from 0.2.0; fixed in 0.32.0
- compose-lint (PyPI): affected from 0.2.0; fixed in 0.32.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123371/ (Markdown: https://insights.sbomify.com/CVE-2026-123371/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123371
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123371
- OSV: https://osv.dev/vulnerability/CVE-2026-123371

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123371/
Summaries are generated and may contain mistakes; the official description above is the record.