CVE-2026-123796

compose-lint: Incomplete fix for GHSA-jf3h-8jvx-vcrg: a run stopped at the finding limit quotes a secret from a CI-generated `.env`

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

Published 09/11/2026, 17:48:15 UTC

Severity and exploitation

Not in CISA KEVSource: LOW

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 23:55: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

This is an incomplete fix for GHSA-jf3h-8jvx-vcrg. 0.32.0 made findings quote the ${NAME} a sibling .env filled in, instead of its value. The same release added a stop at 20,000 findings per document, and that stop is checked before the quoting step. A run that hits it reports the findings graded so far with the resolved values still in them, in text, JSON and SARIF output. That happens with or without --allow-partial-coverage.

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.32.0, < 0.33.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.32.0 before 0.33.0Ecosystem versions	0.33.0

Version evidence: OSV · GHSA-rm8w-w798-g545

View original version evidence (1 explicit versions)

tmatens/compose-lint GitHub Actions

Affected range	Recorded fix
From 0.32.0 before 0.33.0Ecosystem versions	0.33.0
From 2d42617e4c6416f797bbfc6a057950131fa02df3 before 691e08bd1881ada886e3f556d0793079e8114451Git commits	691e08bd1881ada886e3f556d0793079e8114451

Version evidence: OSV · GHSA-rm8w-w798-g545

View original version evidence (2 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-rm8w-w798-g545 ↗Attributed to CISA-ADP

Original source description

Read the full publisher description

Impact

This is an incomplete fix for GHSA-jf3h-8jvx-vcrg. 0.32.0 made findings quote the ${NAME} a sibling .env filled in, instead of its value. The same release added a stop at 20,000 findings per document, and that stop is checked before the quoting step. A run that hits it reports the findings graded so far with the resolved values still in them, in text, JSON and SARIF output. That happens with or without --allow-partial-coverage.

The attack is the one GHSA-jf3h-8jvx-vcrg describes. In a CI workflow that writes secrets into the .env beside the Compose file, a pull request changes a line to image: "${DB_PASSWORD}". It also pushes the document past 20,000 findings, which a few hundred lines can do, because an aliased list is graded once for each service that uses it. The secret's value is quoted in a finding that reaches the job log, the 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 run exits 2, or 0 with --allow-partial-coverage, after the output has been written.

The preconditions are the same as for GHSA-jf3h-8jvx-vcrg. The workflow writes secrets into the .env beside the Compose file and runs on pull requests from authors who should not see them, such as a pull_request_target workflow that lints the pull request's files. Pull requests from forks normally run without secrets, so the common setup is not exposed. The inflated document is visible in the pull request, but the workflow runs before anyone reviews it.

Found during an internal pre-1.0 security review.

Python package. compose-lint 0.32.0. Earlier releases have no finding limit, and their quoting gap is GHSA-jf3h-8jvx-vcrg itself.

GitHub Action. Action tag v0.32.0 is affected. Tags before v0.22.0 install the newest release unless version: is set, so they currently install 0.32.0.

pre-commit hook. rev: v0.32.0.

Docker image. composelint/compose-lint:0.32.0, :0.32 and latest are affected when the .env is mounted with the project.

Patches

No fixed release yet.

Workarounds

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   x-p: &p [ ...200 port mappings... ]
                      services: one service with image: "${DB_PASSWORD}" and ports: *p,
                                plus about 100 more services with ports: *p

compose-lint --format sarif compose.yml exits 2 with "grading stopped at 20000 findings", and the reported findings contain example-secret. The same file with fewer services stays under the limit and quotes ${DB_PASSWORD}. Checked against the 0.32.0 wheel from PyPI, using a synthetic value.

References

6 sources

tmatens/compose-lint · security/advisories/GHSA-rm8w-w798-g545

Public exploit referenceGitHub_M · CISA-ADP

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

Security advisory

tmatens/compose-lint · pull request #978

PatchGitHub_M

tmatens/compose-lint · commit 31ec460

PatchGitHub_M

tmatens/compose-lint · repository

Source reference

tmatens/compose-lint · releases/tag/v0.33.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-123796

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-14

Timeline

All times UTC

9 Nov 2026, 17:48
Advisory published
Publication date supplied by the source.
14 Nov 2026, 01:47
Source updated
Latest modification date supplied by the source.
14 Nov 2026, 02:48
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes

CVE · CVE-2026-1237962026-11-14

Observed 2026-11-14T02:48:04.239Z · upstream updated 2026-11-14T01:47:00.783Z

Prioritization updated

before

[]

after

[
  {
    "source": "CISA-ADP",
    "type": "SSVC",
    "role": "CISA Coordinator",
    "timestamp": "2026-11-14T01:46:16.316958Z",
    "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-14

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-rm8w-w798-g545

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-rm8w-w798-g545 CVE CVE-2026-123796

Enrichment coverage

NVDNo result

Checked 09/11/2026, 18:15:34 UTC

GHSANo result

Checked 09/11/2026, 18:15:34 UTC

EUVDNo result

Checked 09/11/2026, 18:15:34 UTC

EPSSNo result

Checked 09/11/2026, 18:15:34 UTC

Sponsored by MoxsoBuild security habits with adaptive training and phishing simulations.View as JSON

Investigate in your agent.

compose-lint: Incomplete fix for GHSA-jf3h-8jvx-vcrg: a run stopped at the finding limit quotes a secret from a CI-generated `.env`

Severity and exploitation

What this means

Attack conditions

Affected versions

compose-lint

affected

unaffected

unknown

Packages

What to do

Public exploit evidence

Original source description

Impact

Patches

Workarounds

Reproduction

References

Inside the record

Evidence available

Original records

Underlying weaknesses

Timeline

Advisory published

Source updated

Last imported by cve.new

What changed