CVE-2026-123372

compose-lint: A pull request can make compose-lint quote a secret from a CI-generated `.env` into its findings

Products / packages tmatens compose-lint · compose-lint · tmatens/compose-lint

Published 09/11/2026, 17:38:24 UTC

Severity and exploitation

Not in CISA KEVSource: LOW

KEV coverage does not rule out exploitation.

KEV checked 15/11/2026, 00:05:31 UTC

OSV · CVSS:4.0 · 2.3

Assessment 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

GitHub_M · CVSS:4.0 · 2.3

Assessment 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

The headline uses the highest imported catalog score. Assessments can differ by source and CVSS version.

Severity

low2.3

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Exploit reference published

Source-linked evidence; not proof of attacks in the wild or independent validation.

Remediation

Package fixes recorded

Fix versions are recorded for 2 of 2 mapped packages. Check each release branch and any separate product guidance.

What this means

Since 0.22.0, compose-lint fills in ${VAR} references from the .env beside the Compose file, as Compose does. The documentation says values under environment: are never resolved from a .env, "that is where secrets live". But image: values are resolved, and CL-0004 and CL-0019 quote the resolved image in their message and fix text.

Source excerpt · OSV

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

tmatens · GitHub_M

compose-lint

1 range

GitHub_M version evidence

Check a product version

Compare with this publisher’s ranges. This does not inspect your installation.

affected

>= 0.22.0, < 0.32.0

Other versions: unknown

Packages

Compare each installed version with the publisher’s affected ranges. Where a fix is recorded, choose the appropriate release branch and test compatibility before upgrading.

compose-lint PyPI

Affected range	Recorded fix
From 0.22.0 before 0.32.0Ecosystem versions	0.32.0

Version evidence: OSV · GHSA-jf3h-8jvx-vcrg

View original version evidence (10 explicit versions)

tmatens/compose-lint GitHub Actions

Affected range	Recorded fix
From 0.22.0 before 0.32.0Ecosystem versions	0.32.0
From 811ef6b379dbc78d048fcedaf976205705d4a7c3 before 2d42617e4c6416f797bbfc6a057950131fa02df3Git commits	2d42617e4c6416f797bbfc6a057950131fa02df3

Version evidence: OSV · GHSA-jf3h-8jvx-vcrg

View original version evidence (10 explicit versions)

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

Use the recorded fix for your release branch. Review the publisher’s instructions and test compatibility before upgrading.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

The sources identify public exploit references. We have not independently tested them; their availability does not establish exploitation in the wild.

tmatens/compose-lint · security/advisories/GHSA-jf3h-8jvx-vcrg ↗Attributed to CISA-ADP

Original source description

Read the full publisher description

Impact

Since 0.22.0, compose-lint fills in ${VAR} references from the .env beside the Compose file, as Compose does. The documentation says values under environment: are never resolved from a .env, "that is where secrets live". But image: values are resolved, and CL-0004 and CL-0019 quote the resolved image in their message and fix text.

Some CI workflows write secrets into that .env before linting or building. In such a workflow, a pull request that changes one line to image: "${DB_PASSWORD}", or image: "nginx:${DB_PASSWORD}", gets the secret's value quoted in a finding. The finding reaches the job log, JSON output, and the SARIF uploaded to Code Scanning. GitHub masks registered secrets in the job log, but not in uploaded JSON or SARIF artifacts or in Code Scanning alert text. The pass/fail result is not affected.

This needs a workflow that writes secrets into the .env beside the Compose file and runs on pull requests from authors who should not see them. Pull requests from forks normally run without secrets, so the common setup is not exposed, which is why this is scored as low confidentiality impact. Where the conditions hold, such as a pull_request_target workflow, pull requests from branches in the same repository, or a self-hosted runner that keeps a populated .env in the checkout, the whole value is disclosed.

Found during an internal pre-1.0 security review.

GitHub Action. Action tags v0.22.0 through v0.31.0 install their own compose-lint version and are affected. Earlier tags install the newest release unless version: is set, and so currently install an affected one.

Docker image. composelint/compose-lint tags 0.22.0 through 0.31.0, the matching minor tags, and latest are affected when the .env is mounted with the project.

Patches

Fixed in 0.32.0. Rules still grade the value the sibling .env substituted, but findings, fix guidance and notes quote the ${NAME} reference in its place, in text, JSON and SARIF. A value shorter than 8 characters is shown as written, because short values are also words the guidance itself uses; docs/what-a-run-reads.md states this limit.

Workarounds

Upgrade to 0.32.0 or later.
Run with --no-env, which skips the sibling .env.
Don't write secrets into the .env beside the Compose file in a job that lints untrusted pull requests.

Reproduction

project/.env          DB_PASSWORD=example-secret      (written by CI, not committed)
project/compose.yml   services: {web: {image: "${DB_PASSWORD}"}}

compose-lint --format sarif compose.yml reports CL-0004 with the message Image 'example-secret' has no tag, ....

References

6 sources

tmatens/compose-lint · security/advisories/GHSA-jf3h-8jvx-vcrg

Public exploit referenceGitHub_M · CISA-ADP

nvd.nist.gov/vuln/detail/CVE-2026-123372

Security advisory

tmatens/compose-lint · pull request #944

PatchGitHub_M

tmatens/compose-lint · commit 977da97

PatchGitHub_M

tmatens/compose-lint · repository

Source reference

tmatens/compose-lint · releases/tag/v0.32.0

Release notesGitHub_M

Inside the record

Evidence available

Package identity

Version evidence

Remediation guidance · not supplied

Weakness classification

Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-123372

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-200 ↗

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

GitHub_M

CWE-532 ↗

CWE-532: Insertion of Sensitive Information into Log File

GitHub_M

Contributing organizations · 2

GitHub_M

Assigning organization

2026-11-09

CISA-ADP

Additional data publisher

2026-11-13

Timeline

All times UTC

9 Nov 2026, 17:38
Advisory published
Publication date supplied by the source.
13 Nov 2026, 12:29
Source updated
Latest modification date supplied by the source.
13 Nov 2026, 22:34
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes

CVE · CVE-2026-1233722026-11-13

Observed 2026-11-13T22:34:40.844Z · upstream updated 2026-11-13T12:29:34.320Z

Prioritization updated

before

[]

after

[
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-13T12:28:46.518093Z",
    "decisions": [
      {
        "name": "Exploitation",
        "value": "poc"
      },
      {
        "name": "Automatable",
        "value": "no"
      },
      {
        "name": "Technical Impact",
        "value": "partial"
      }
    ]
  }
]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.

Reading the signals

Severity · CVSS: Technical impact and attack conditions. The headline is the highest imported catalog score; sources may disagree.
Observed exploitation · KEV: An absent or unavailable KEV listing does not establish that exploitation has not occurred.
Predicted exploitation · EPSS: No EPSS estimate available in this record.

CISA-ADP · SSVC

CISA Coordinator · 2026-11-13

Exploitation: poc
Automatable: no
Technical Impact: partial

SSVC describes the publisher’s decision context. Your organization’s exposure and priorities may differ.

Record identifiers

Aliases: GHSA-jf3h-8jvx-vcrg

Source evidence

Request a correction or dispute

Start with the assigning organization for this record. Include the CVE ID, the disputed information, and supporting evidence. A dispute does not itself reject a record.

Find the responsible CNA →Official dispute and escalation process ↗

OSV GHSA-jf3h-8jvx-vcrg CVE CVE-2026-123372