Skip to main content
VulnerabilityPublished Updated

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

Affects coollabsio coolifySource CVE Database V5

0

Not known to be exploited · CVSS 9.4 Critical · fixed in 4.0.0 : patch coollabsio coolify as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.2% chance of exploitation in 30 days – higher than 88% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.0
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 23 Dec 2025

  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

Affected software

ProductAffectedFixed in
GitHubcoollabsio/coolifypkg:github/coollabsio/coolifyOther threatsAffected
  • =4.0.0-beta.451
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 CVE-2025-66212, organizations should immediately upgrade Coolify installations to version 4.0.0-beta.451 or later, where the vulnerability is patched. Until the upgrade is applied, restrict application and service management permissions to the minimum necessary users, enforcing strict access controls and multi-factor authentication to reduce the risk of unauthorized exploitation. Conduct thorough audits of user permissions and remove any unnecessary management privileges. Implement monitoring and alerting for unusual command execution or privilege escalation activities on managed servers. Consider isolating Coolify management interfaces behind VPNs or internal networks to limit exposure. Additionally, review proxy configuration filename inputs and sanitize or validate them at the application level if custom modifications exist. Regularly back up critical data and configurations to enable recovery in case of compromise. Finally, maintain an incident response plan tailored to potential command injection attacks to ensure rapid containment and remediation.

Description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to version 4.0.0-beta.451, an authenticated command injection vulnerability in the Dynamic Proxy Configuration Filename handling allows users with application/service management permissions to execute arbitrary commands as root on managed servers. Proxy configuration filenames are passed to shell commands without proper escaping, enabling full remote code execution. Version 4.0.0-beta.451 fixes the issue.

References

Community reviews

Loading reviews…