CVE-2026-123373

CVE-2026-123373 is a low-severity security vulnerability in compose-lint (pip), affecting versions >= 0.2.0, <= 0.24.0. It is fixed in 0.25.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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

Workarounds

  • Upgrade to 0.25.0 or later.
  • On older versions, don't run compose-lint on untrusted pull requests on a machine whose files outside the checkout hold credentials. --no-env closes the COMPOSE_FILE and env_file: routes, but not the others.

Reproduction

project/compose.yml -> /path/outside/project/credentials   (symlink)

compose-lint --format sarif compose.yml on 0.24.0 exits 2, and the SARIF notification quotes a line of the linked file. On 0.25.0 the error gives only the line and column.

Impact

Like Docker Compose, compose-lint follows symlinks when it reads a project's files. Unlike Compose, compose-lint up to 0.24.0 could then put the contents of a file from outside the project into its output, where the author of a pull request can read it.

A pull request can commit a symlink, under a name compose-lint reads, pointing at a file on the CI runner:

  • The Compose file itself (0.2.0–0.24.0). A compose.yml that is a symlink, whether the pre-commit hook passes its name or the Action or a bare run finds it.
  • compose.override.yml (0.22.0–0.24.0), which compose-lint merges automatically.
  • A COMPOSE_FILE entry (0.22.0–0.24.0) in a .env beside the Compose file.

When the target is not valid YAML, the parse error quotes the line it failed on. Docker Compose, given the same file, reports only a line number. That line reaches standard error (the job log), JSON errors[], and the SARIF toolExecutionNotifications, which the Action uploads to Code Scanning.

A fourth route: from 0.23.0, a symlinked env_file: target makes CL-0020 and CL-0021 report the credential-like key names in a file outside the project. Values are not printed.

What can be read is one line of a file chosen by path, at the point where the YAML parser fails, which the attacker cannot choose; or key names. A symlink to /proc/self/environ gave neither in testing. The pass/fail result is not affected. On a public repository the job log is visible to the pull request's author.

Found during an internal pre-1.0 security review.

GitHub Action. Action tags v0.18.0 through v0.24.0 install their own compose-lint version and are affected. Earlier tags install the newest release unless version: is set; they were affected while that was 0.24.0 or earlier.

Docker image. composelint/compose-lint tags 0.3.3 through 0.24.0, and the matching minor tags, are affected. Inside the container a symlink resolves within the container, so what can be read is the container's own files and anything mounted into it. Fixed from 0.25.0.

Affected versions

compose-lint (>= 0.2.0, <= 0.24.0) tmatens/compose-lint (>= 0.2.0, <= 0.24.0)

Security releases

compose-lint → 0.25.0 (pip) tmatens/compose-lint → 0.25.0 (actions)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Fixed in 0.25.0. Parse errors no longer quote the source line; the error and its line and column are kept. env_file: targets and COMPOSE_FILE entries that resolve outside the project are also refused, with the existing outside-the-project note. Symlinks that stay inside the project still work.

From 0.25.0 through 0.31.0, a committed symlink to a target that is itself a Compose file could still be read, and its values could reach findings. 0.32.0 stops following a discovered, named or override Compose file whose link leaves the checkout.

A related gap for the sibling .env file is covered by GHSA-6wcv-rj3c-mhv3, and one for a symlinked .compose-lint.yml by GHSA-88f4-frh5-gmcr.

Frequently Asked Questions

  1. What is CVE-2026-123373? CVE-2026-123373 is a low-severity security vulnerability in compose-lint (pip), affecting versions >= 0.2.0, <= 0.24.0. It is fixed in 0.25.0.
  2. Which packages are affected by CVE-2026-123373?
    • compose-lint (pip) (versions >= 0.2.0, <= 0.24.0)
    • tmatens/compose-lint (actions) (versions >= 0.2.0, <= 0.24.0)
  3. Is there a fix for CVE-2026-123373? Yes. CVE-2026-123373 is fixed in 0.25.0. Upgrade to this version or later.
  4. Is CVE-2026-123373 exploitable, and should I be worried? Whether CVE-2026-123373 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2026-123373 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2026-123373?
    • Upgrade compose-lint to 0.25.0 or later
    • Upgrade tmatens/compose-lint to 0.25.0 or later

Other vulnerabilities in compose-lint

Stop the waste.
Protect your environment with Kodem.