Skip to main content
VulnerabilityPublished

CVE-2026-125121: tmatens compose-lint · Log Injection

Affects tmatens compose-lintSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.32.0 when convenient.

Data as of 10 Nov 2026, 17:04 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.05.3
Patch
Available – fixed in 0.32.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade tmatens compose-lint to 0.32.0.

Affected software

ProductAffectedFixed in
tmatenscompose-lintAffected
  • >=0.31.0 <0.32.0
Fixed in
  • 0.32.0

AI-suggested

Upgrade compose-lint to version 0.32.0 or later, where this issue is fixed. No other mitigation is required as the GitHub Action disables command processing and is not affected.

Description

compose-lint versions 0.31.0 up to but not including 0.32.0 contain a vulnerability where improper output neutralization for logs allows untrusted Compose values or repository paths starting with Unicode whitespace followed by :: to be interpreted as GitHub Actions workflow commands in CI environments. This flaw does not affect the linting result and is fixed in version 0.32.0.

References

Community reviews

Loading reviews…