{"answers":{"affected":"2 open source packages ship an affected version, including tmatens/compose-lint and compose-lint.","exploited":"There is no known exploitation of CVE-2026-123372 in the wild and no public exploit code.","exposure":"","fix":"Upgrade tmatens/compose-lint to 0.32.0 or later.","what":"CVE-2026-123372 is a low-severity vulnerability in tmatens compose-lint, published on 9 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-123372 and fix it if it is affected.\n\nWhat it is: CVE-2026-123372 is a low-severity vulnerability in tmatens compose-lint, published on 9 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-123372 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tmatens/compose-lint (GitHub Actions): affected from 0.22.0; fixed in 0.32.0\n- compose-lint (PyPI): affected from 0.22.0; fixed in 0.32.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-123372/ (Markdown: https://insights.sbomify.com/CVE-2026-123372/index.md)","id":"CVE-2026-123372","markdown":"https://insights.sbomify.com/CVE-2026-123372/index.md","name":"CVE-2026-123372","record":{"aliases":["GHSA-jf3h-8jvx-vcrg"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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.","ecosystems":["GitHub Actions","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"compose-lint: A pull request can make compose-lint quote a secret from a CI-generated `.env` into its findings","id":"CVE-2026-123372","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"compose-lint: A committed symlink makes compose-lint quote a file from outside the project into its output","id":"CVE-2026-123373"},"nickname":null,"packages":[{"ecosystem":"GitHub Actions","fixed":["0.32.0"],"introduced":["0.22.0"],"last_affected":[],"package":"tmatens/compose-lint","purl":null,"source":"GHSA-jf3h-8jvx-vcrg"},{"ecosystem":"PyPI","fixed":["0.32.0"],"introduced":["0.22.0"],"last_affected":[],"package":"compose-lint","purl":null,"source":"GHSA-jf3h-8jvx-vcrg"}],"prev":{"headline":"compose-lint: A `.compose-lint.yml` symlinked outside the project is read, and a parse error quotes part of the target","id":"CVE-2026-123371"},"products":["compose-lint"],"published":"2026-11-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-09","vendors":["tmatens"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-123372/"}