---
id: "CVE-2026-123368"
page: "https://infrastack.ai/live/CVE-2026-123368"
kind: "vulnerability"
aliases: ["CVE-2026-123368"]
title: "compose-lint: symlinked .env leaks runner environment into scan output"
severity: "low"
cvss: 2.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["ci", "docker-compose", "github-actions", "package"]
not_affected_if: ["no-untrusted-pull-requests", "version-0.31.0-or-later"]
published_at: "2026-11-09T18:17:25+00:00"
first_seen_at: "2026-11-09T18:27:55+00:00"
updated_at: "2026-11-09T18:29:28+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-123368", "first_seen_at": "2026-11-09T18:27:55+00:00"}]
exploit_sources: []
---

# compose-lint: symlinked .env leaks runner environment into scan output

Link for people: https://infrastack.ai/live/CVE-2026-123368 (this .md is for agents)

compose-lint follows a sibling .env symlink that points outside the project without its containment check. A crafted pull request can make runner file or process environment data appear in findings, logs, and SARIF alerts.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version of compose-lint with `compose-lint --version` or the lockfile entry.
- Look in CI workflows that run compose-lint on untrusted pull requests for environment-bearing setups.

## Fix

- compose-lint: move to `0.31.0`.

## Timeline

- 2026-11-09T18:27:55+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-123368

## Documents

- [advisory] Vendor advisory: github.com https://github.com/tmatens/compose-lint/security/advisories/GHSA-6wcv-rj3c-mhv3
- [fix] Patch: github.com https://github.com/tmatens/compose-lint/commit/c43204ad4dab11d54e20574a52bc4e5835246ca5
- [fix] Release notes: github.com https://github.com/tmatens/compose-lint/releases/tag/v0.31.0

## From the sources

compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. From 0.22.0 until 0.31.0, compose-lint follows a sibling .env symbolic link outside the project without applying its normal containment check. From 0.28.0, the same gap also affects an include project_directory link outside the project. A pull request can reference a variable from the linked file, causing substitution to place runner file or process-environment data into finding messages written to logs, JSON, SARIF artifacts, and Code Scanning alerts. Reading /proc/self/environ can expose the remainder of the linter process environment because NUL-separated entries are treated as one value, although disclosure requires a workflow that processes untrusted changes with useful environment data and GitHub normally withholds secrets from fork pull requests. The pass or fail result is not changed. This issue is fixed in version 0.31.0.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_