Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.3amended

compose-lint: Workflow command injection through SARIF-directory errors triggered by pull request symlinks

CVE-2026-125125GHSA-xcf7-88g6-7xr8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (tmatens/compose-lint 0.32.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact In Action tags v0.30.0 and v0.31.0, when `sarif-file:` names a file in a subdirectory that can't be created, the Action prints the directory's resolved path in an error message. In v0.31.0 that message is outside the window in which the Action turns command processing off, and v0.30.0 has no such window. A pull request can commit a symlink on that path to a directory whose name contains a newline followed by a command. A pull request can therefore create annotations, fold or hide parts of the job log, or issue other commands the runner accepts, when CI runs compose-lint over it, before anyone reviews it. The pass/fail result is not changed. Only the Action is affected, and only when `sarif-file:` points into a subdirectory. The documented setup, `sarif-file: results.sarif` at the repository root, is not affected. The `compose-lint` package, the pre-commit hook and the Docker image do not print this message. Found during an internal pre-1.0 security review. It was first…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-xcf7-88g6-7xr8

  2. Revision 1 · created ·

    Published from ghsa record GHSA-xcf7-88g6-7xr8

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-125125

Advisory: compose-lint: Workflow command injection through SARIF-directory errors triggered by pull request symlinks
IDs: CVE-2026-125125, GHSA-xcf7-88g6-7xr8
Record: https://patchnext.com/advisories/cve-2026-125125 (revision 2, source checked 11 Nov 2026, 07:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tmatens/compose-lint 0.32.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- GitHub Actions tmatens/compose-lint: affected >= 0.30.0, < 0.32.0; fixed in 0.32.0

## Suggested inspection (read-only)
- GitHub Actions tmatens/compose-lint: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tmatens/compose-lint.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-xcf7-88g6-7xr8 (GitHub-reviewed advisory GHSA-xcf7-88g6-7xr8 lists affected ranges: GitHub Actions tmatens/compose-lint >=0.30.0 <=0.31.0)
- Verified: https://osv.dev/vulnerability/GHSA-xcf7-88g6-7xr8 (OSV record GHSA-xcf7-88g6-7xr8 lists affected ranges: GitHub Actions tmatens/compose-lint >=0.30.0 <0.32.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…