Skip to main content
VulnerabilityPublished

CVE-2025-64419: coollabsio coolify · Command Injection

Affects coollabsio coolifySource CVE Database V5

0

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

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.7Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.0-beta.445
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A: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.445.

Affected software

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

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

AI-suggested

To mitigate this vulnerability, European organizations should immediately upgrade all Coolify instances to version 4.0.0-beta.445 or later, where the issue is fixed. Until upgrades are complete, restrict the creation of applications from untrusted or external repositories, especially those using the "docker compose" build pack. Implement strict repository whitelisting and code review processes to prevent malicious code injection. Employ network segmentation and least privilege principles to limit the impact of potential compromises. Monitor Coolify logs and system activity for unusual command executions or repository usage patterns. Additionally, consider container runtime security tools to detect anomalous behaviors. Regularly audit and update DevOps toolchains to ensure dependencies and management platforms are current and secure.

Description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to version 4.0.0-beta.445, parameters coming from docker-compose.yaml are not sanitized when used in commands. If a victim user creates an application from an attacker repository (using build pack "docker compose"), the attacker can execute commands on the Coolify instance as root. Version 4.0.0-beta.445 fixes the issue.

References

Community reviews

Loading reviews…