Skip to main content
VulnerabilityPublished

CVE-2026-123373: tmatens compose-lint · Link Following

Affects tmatens compose-lintSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.3 Low : upgrade to 0.25.0 when convenient.

Data as of 9 Nov 2026, 18:04 UTC

CVSS 4.0 base score
2.3Low
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.02.3
Patch
Available – fixed in 0.25.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 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 9 Nov 2026.

What to do

Upgrade tmatens compose-lint to 0.25.0.

Affected software

ProductAffectedFixed in
tmatenscompose-lintAffected
  • >=0.2.0 <0.25.0
Fixed in
  • 0.25.0

AI-suggested

Upgrade compose-lint to version 0.25.0 or later, where this issue is fixed. No other mitigation is required as the vulnerability is resolved in this official fix.

Description

compose-lint versions from 0.2.0 up to but not including 0.25.0 follow symbolic links controlled by a project that point to Compose files outside the project directory. This affects compose.override.yml, COMPOSE_FILE entries from 0.22.0, and env_file targets from 0.23.0. If an external Compose-related target fails YAML parsing, error messages may include attacker-controlled lines, potentially exposing credential-like key names. The vulnerability does not allow control over exact parser failure lines or values from env_file, and the pass/fail result remains unchanged. The issue is fixed in version 0.25.0.

References

Community reviews

Loading reviews…