CVE-2026-125125: compose-lint log injection in SARIF errors

Summary

The compose-lint GitHub Action, in releases made before the fix, prints a resolved directory path from a failed SARIF subdirectory creation without effectively suppressing workflow commands, but only when its sarif-file points into a subdirectory. A remote attacker without logging in can exploit this through a pull request that commits a symlink to a directory whose name contains a newline followed by a workflow command, which causes those commands to run in the job log.

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. From version 0.30.0 until 0.32.0, the compose-lint GitHub Action prints the resolved directory from a failed sarif-file subdirectory creation without effective command suppression. Version 0.30.0 has no stop-commands window, while version 0.31.0 prints this error outside its stop-commands window. A pull request can place a committed symlink on that path to a directory whose name contains a newline followed by a workflow command, causing the SARIF-directory error to issue commands in the job log. Only the Action with sarif-file pointing into a subdirectory is affected; a workspace-root SARIF file, the compose-lint package, the pre-commit hook, and the Docker image do not expose this message. This issue is fixed in version 0.32.0.

cve.now Index

9Pcve.now Index 9 of 100 · methodology v3 · provisional

Exploitation0/40No signal
Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
Reach?/20Unknown. No tracked technology or package matched
Severity2.3/10CVSS 2.3
No patch0/5No signal

What would change the score

Would score about 64 if added to CISA KEV
Would score about 59 if CISA's SSVC rates exploitation active
Would score about 24 if advisories confirm default setups are exposed

How the score works · Rankings

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-125125 (compose-lint: A symlink in a pull request can issue workflow commands through the compose-lint Action's SARIF-directory error message), 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-125125 (entry last updated 2026-11-10):
Affected:
- tmatens compose-lint: from 0.30.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-125125 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125125 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/tmatens/compose-lint/security/advisories/GHSA-xcf7-88g6-7xr8
- 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.

Entry: https://cve.now/CVE-2026-125125
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-125125.

Timeline

Nov 10, 2026, 4:55 PM UTCCVE published
Nov 10, 2026, 5:01 PM UTCFirst seen by cve.now
Nov 10, 2026, 6:19 PM UTCCISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
Nov 10, 2026, 7:04 PM UTCRecord last updated

Affected versions

tmatens compose-lint
From 0.30.0 · fixed in 0.32.0

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

Advisory
GitHub · tmatens/compose-lint · Advisory GHSA-xcf7-88g6-7xr8

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-125125
Record
NVD · CVE-2026-125125

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-125125

Is CVE-2026-125125 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-125125?

compose-lint: from 0.30.0 before 0.32.0.Source: cve.now feed data

How do I fix CVE-2026-125125?

Upgrade to a fixed version: 0.32.0.Source: cve.now feed data

compose-lint: A symlink in a pull request can issue workflow commands through the compose-lint Action's SARIF-directory error message