Skip to main content
VulnerabilityPublished

CVE-2025-59156: coollabsio coolify · OS Command Injection

Affects coollabsio coolifySource CVE Database V5

0

Not known to be exploited · CVSS 9.4 Critical : upgrade to 4.0.0-beta.420.7 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.0-beta.420.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade coollabsio coolify to 4.0.0-beta.420.7.

Affected software

ProductAffectedFixed in
coollabsiocoolifyAffected
  • <4.0.0-beta.420.7
Fixed in
  • 4.0.0-beta.420.7
GitHubcoollabsio/coolifypkg:github/coollabsio/coolifyOther threatsAffected
  • =4.0.0-beta.420.7
Fixed in–

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

AI-suggested

  1. Immediately upgrade all Coolify instances to version 4.0.0-beta.420.7 or later to apply the official patch.
  2. Restrict project creation and update permissions to trusted, high-privileged users only, minimizing the risk of malicious Docker Compose injection.
  3. Implement strict input validation and sanitization on any user-supplied configuration data related to Docker Compose files.
  4. Monitor Docker Compose configurations and deployment workflows for unauthorized or suspicious changes using file integrity monitoring and audit logging.
  5. Employ container runtime security tools that can detect and prevent host filesystem mounts or privilege escalations.
  6. Conduct regular security assessments and penetration tests focusing on container escape vectors.
  7. Isolate Coolify management interfaces behind strong network controls and multi-factor authentication to reduce exposure.
  8. Educate administrators and developers about the risks of improper configuration and the importance of applying security patches promptly.

Description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to version 4.0.0-beta.420.7, a Remote Code Execution (RCE)*vulnerability exists in Coolify's application deployment workflow. This flaw allows a low-privileged member to inject arbitrary Docker Compose directives during project creation or updates. By defining a malicious service that mounts the host filesystem, an attacker can achieve root-level command execution on the host OS, completely bypassing container isolation. Version 4.0.0-beta.420.7 contains a patch for the issue.

References

Community reviews

Loading reviews…