---
id: "CVE-2026-123372"
page: "https://infrastack.ai/live/CVE-2026-123372"
kind: "vulnerability"
aliases: ["CVE-2026-123372"]
title: "compose-lint: linter echoes .env secrets into logs and scan reports"
severity: "low"
cvss: 2.3
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["ci", "compose-lint", "docker-compose", "github-actions", "package"]
not_affected_if: ["fork-prs-only", "no-secrets-in-env-file", "version-0.32.0-or-later"]
published_at: "2026-11-09T18:17:26+00:00"
first_seen_at: "2026-11-09T18:27:56+00:00"
updated_at: "2026-11-09T18:29:29+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-123372", "first_seen_at": "2026-11-09T18:27:56+00:00"}]
exploit_sources: []
---

# compose-lint: linter echoes .env secrets into logs and scan reports

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

compose-lint, a Docker Compose security linter, copies values from a sibling .env file into finding messages when an image field references them. In a CI workflow that writes secrets to that file and lints untrusted pull-request content, an attacker can make a secret's full value appear in job logs, JSON output, SARIF files and Code Scanning alerts.

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

## How to check

- Run `compose-lint --version` or check the pinned version in your lockfile or workflow file; affected versions are `0.22.0` through `0.32.0`.
- Check whether CI writes secrets into a `.env` file next to a Compose file and then runs compose-lint on pull-request content, including `pull_request_target` workflows.
- Check whether a retained `.env` file is left on a self-hosted runner where compose-lint runs.

## Fix

- compose-lint: move to `0.32.0`

## Timeline

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

## Documents

- [advisory] Vendor advisory: github.com https://github.com/tmatens/compose-lint/security/advisories/GHSA-jf3h-8jvx-vcrg
- [fix] Patch: github.com https://github.com/tmatens/compose-lint/commit/977da9724789264c2662afe47f79220e915442c2
- [fix] Release notes: github.com https://github.com/tmatens/compose-lint/releases/tag/v0.32.0

## From the sources

compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. From 0.22.0 until 0.32.0, compose-lint substitutes values from a sibling .env file into image fields and quotes the resolved value in CL-0004 and CL-0019 finding messages and fix text. In a workflow that writes secrets into that file and then lints untrusted pull-request content, an attacker can reference a secret variable so its whole value reaches the job log, JSON output, SARIF artifacts, and Code Scanning alerts. Fork pull requests normally lack secrets, so exploitation requires a secret-bearing workflow such as pull_request_target, same-repository branches, or a retained .env on a self-hosted runner, and the pass or fail result is unchanged. This issue is fixed in version 0.32.0.

---

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