compose-lint: Text in a pull request can issue CI workflow commands through compose-lint 0.31.0's JSON and SARIF output on stdout
- Exploited
- No known exploitation
- Fix
- Fixed in 0.32.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.32.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
compose-lint, a Docker Compose security linter, does not sanitize the `##[` workflow-command opener in its JSON or SARIF stdout output, so a remote attacker without logging in can use values such as service names in a pull request to issue CI workflow commands through a job log. This requires a user to run the tool in a way that prints that output to the CI job log, and writing the output to a file or using the compose-lint GitHub Action is not affected.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
compose-lint is a Docker Compose security linter that identifies dangerous misconfigurations before deployment. In version 0.31.0, compose-lint does not sanitize the ##[ workflow-command opener inside strings written by --format json or --format sarif to stdout. A pull request can place that opener in a service name or other Compose value, and the GitHub Actions runner recognizes it even in the middle of a serialized line when the package, pre-commit hook, or Docker image prints JSON or SARIF to the job log. Writing the output to a file and using the compose-lint GitHub Action are not affected, and the flaw does not change the lint pass or fail result. This issue is fixed in version 0.32.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach10/20Affects PyPI packages
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.32.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125122 (compose-lint: Text in a pull request can issue CI workflow commands through compose-lint 0.31.0's JSON and SARIF output on stdout), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-125122 (entry last updated 2026-11-10): Affected: - tmatens compose-lint: versions 0.31.0 - PyPI package compose-lint: from 0.31.0, fixed in 0.32.0 Fixed versions: 0.32.0. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-125122 is not listed as of cve.now's last read. This KEV status is for CVE-2026-125122 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (PyPI): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/tmatens/compose-lint/security/advisories/GHSA-hr4h-4c45-v4q4 - https://github.com/tmatens/compose-lint/pull/945 - https://github.com/tmatens/compose-lint/commit/542e63126f795564a65c63887ea0dc558a500688 - https://github.com/tmatens/compose-lint/releases/tag/v0.32.0 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-125122 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125122.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- tmatens compose-lint
0.31.0
- compose-lintPyPI
From 0.31.0 · fixed in 0.32.0
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125122
Is CVE-2026-125122 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-125122?
compose-lint: version 0.31.0. compose-lint (PyPI): from 0.31.0 before 0.32.0.Source: cve.now feed data
How do I fix CVE-2026-125122?
Upgrade to a fixed version: 0.32.0.Source: cve.now feed data