Skip to main content
VulnerabilityPublished

CVE-2026-42204: coollabsio coolify · OS Command Injection

Affects coollabsio coolifySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 4.0.0-beta.474 soon.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.0-beta.474
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 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 18 Nov 2026.

What to do

Upgrade coollabsio coolify to 4.0.0-beta.474.

Affected software

ProductAffectedFixed in
coollabsiocoolifyAffected
  • >=4.0.0-beta.471 <4.0.0-beta.474
Fixed in
  • 4.0.0-beta.474
GitHubcoollabsio/coolifypkg:github/coollabsio/coolifyOther threatsAffected
  • =4.0.0-beta.471
  • =4.0.0-beta.472
  • =4.0.0-beta.473
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Coolify version 4.0.0-beta.474 or later, where this vulnerability has been fixed. No other mitigation or temporary workaround is indicated.

Description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. From 4.0.0-beta.471 through 4.0.0-beta.473, a regression in SHELL_SAFE_COMMAND_PATTERN allowed ampersands in custom Docker Compose build, start, and pre/post-deployment command fields, allowing an authenticated team member to inject shell commands that execute on the host. This issue is fixed in version 4.0.0-beta.474.

References

Community reviews

Loading reviews…