Is CVE-2026-123368 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-123368 being exploited in the wild.

How severe is CVE-2026-123368?

Low severity, with a CVSS score of 3.1, published 9 November 2026.

Which products and versions are affected?

tmatens/compose-lint (GitHub Actions) >= 0.22.0, = 0.22.0, <= 0.30.0, ECOSYSTEM:introduced=0.22.0,fixed=0.31.0; Tmatens Compose-Lint 0.22.0 through 0.30.x.

Is there a fix for CVE-2026-123368?

Yes. tmatens/compose-lint (GitHub Actions): upgrade to 0.31.0 or later; compose-lint (PyPI): upgrade to 0.31.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-123368 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-123368?

Check whether you run tmatens/compose-lint (GitHub Actions), compose-lint (PyPI) or Tmatens Compose-Lint at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-123368: compose-lint symlink path traversal environment variable exposure

Q: Is there a fix for CVE-2026-123368?

Yes. tmatens/compose-lint (GitHub Actions): upgrade to 0.31.0 or later; compose-lint (PyPI): upgrade to 0.31.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-123368 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-123368?

Check whether you run tmatens/compose-lint (GitHub Actions), compose-lint (PyPI) or Tmatens Compose-Lint at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-123368 · Severity: low · CVSS 3.1 · Published 2026-11-09

compose-lint is a security linter for Docker Compose configurations that checks for dangerous settings before deployment. Versions 0.22.0 through 0.30.x follow symbolic links in .env files and include project directories outside the project boundary, allowing an attacker to read the linter's process environment (including sensitive variables) by linking to /proc/self/environ. When processing untrusted Docker Compose files in CI/CD workflows, exposed environment variables could leak secrets or system information to logs and scanning alerts.

Technologies: tmatens/compose-lint (GitHub Actions), compose-lint (PyPI), Tmatens Compose-Lint. Vendors: GitHub Actions, PyPI, Tmatens.

Quick answers

Is CVE-2026-123368 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-123368 being exploited in the wild.
How severe is CVE-2026-123368?: Low severity, with a CVSS score of 3.1, published 9 November 2026.
Which products and versions are affected?: tmatens/compose-lint (GitHub Actions) >= 0.22.0, <= 0.30.0, ECOSYSTEM:introduced=0.22.0,fixed=0.31.0|GIT:introduced=811ef6b379dbc78d048fcedaf976205705d4a7c3,fixed=a6a7a76736de1c72abfa96c41ff8af556ffdc55f; compose-lint (PyPI) >= 0.22.0, <= 0.30.0, ECOSYSTEM:introduced=0.22.0,fixed=0.31.0; Tmatens Compose-Lint 0.22.0 through 0.30.x.
Is there a fix for CVE-2026-123368?: Yes. tmatens/compose-lint (GitHub Actions): upgrade to 0.31.0 or later; compose-lint (PyPI): upgrade to 0.31.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-123368 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-123368?: Check whether you run tmatens/compose-lint (GitHub Actions), compose-lint (PyPI) or Tmatens Compose-Lint at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

tmatens/compose-lint (GitHub Actions): upgrade to 0.31.0 or later
compose-lint (PyPI): upgrade to 0.31.0 or later
```
pip install "compose-lint>=0.31.0"
```

Technical details

A path traversal vulnerability in compose-lint's .env and include project_directory handling fails to enforce containment checks for symbolic links pointing outside the project. An attacker can craft a malicious Compose file that references variables from a symlink target (such as /proc/self/environ), causing those values to be substituted into finding messages written to logs, JSON reports, SARIF artifacts, and GitHub Code Scanning alerts. The linter's process environment is NUL-separated, so reading /proc/self/environ exposes all remaining environment entries as a single value.

Affected products

tmatens compose-lint 0.22.0 through 0.30.x

Identifiers

CVE-2026-123368
GHSA-6wcv-rj3c-mhv3

Timeline

2026-11-09: disclosed
2026-09-26: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.