CVE-2026-123371 · Package
NO FIX YET · SEE WHAT TO DO
compose-lint follows a .compose-lint.yml symbolic link to a file outside the project, and when that file fails YAML parsing it prints about 30 characters of its content into logs and SARIF output. A pull request can point the link at a runner credential file, so public CI logs or Code Scanning results may reveal part of that secret.
first public Sep 28, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams that run the compose-lint GitHub Action or CLI on pull requests, especially on public repositories where logs and Code Scanning results are visible. Versions from 0.2.0 up to but not including 0.32.0 are exposed; the attacker cannot choose the exact line disclosed, only partial content of the target file appears.
Not affected if no-pull-request-triggers, private-repositories, version-0.32.0-or-later
Who cares ci, compose-lint, docker-compose, github-actions
compose-lint --version or the action version pinned in the workflow0.32.0compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. From 0.2.0 until 0.32.0, compose-lint automatically follows a .compose-lint.yml policy-file symbolic link outside the project and includes part of the target line when that external file fails YAML parsing. A pull request can point the policy file at a runner credential file, causing about 30 characters around an attacker-uncontrolled parse position to appear in standard error, JSON errors, and SARIF tool execution notifications uploaded by the GitHub Action. The run exits with an error and the attacker cannot select the exact disclosed line, but public logs or Code Scanning output can reveal part of the target. This issue is fixed in version 0.32.0.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.