External risk intelligence

Coolify Command Injection Allows Root Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2025-66212

Coolify is a self-hostable server and application management platform designed to be used as a central dashboard or control panel for infrastructure. Such administrative management interfaces are commonly deployed as web-based, internet-reachable services to allow for remote management of servers and applications, fitting the pattern of an externally reachable management surface.

OS Command Injection

Coollabs Coolify

before 4.0.04.0.0

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A command injection vulnerability exists in Coolify, a tool for managing servers and applications. This flaw allows authenticated users with management permissions to execute arbitrary commands as the root user on affected servers by manipulating proxy configuration filenames.

  • Unauthenticated users can execute commands as root.
  • It impacts server and application management.
  • Confirm relevance and exposure for management tools.

Attack Path

How an attacker could exploit the issue

An attacker with permission to manage applications or services can exploit this vulnerability by manipulating proxy configuration filenames. These filenames are processed without proper security checks, allowing them to be used in shell commands, leading to arbitrary command execution with root privileges on the server.

  • Authenticated user with management permissions.
  • Unsanitized proxy configuration filename input.
  • Arbitrary command execution as root.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an authenticated user with application or service management permissions could execute arbitrary commands as root on managed servers. This is possible because proxy configuration filenames are not properly escaped when passed to shell commands, potentially allowing for full remote code execution.

  • System commands could be executed.
  • Unsanitized filenames could trigger execution.
  • Compromise of managed servers.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Coolify application owner, or the team managing the infrastructure where Coolify is deployed, is responsible for addressing this vulnerability. The first step is to identify all instances of Coolify, confirm their accessibility and business criticality, and then establish the responsible parties for remediation.

  • Application and infrastructure teams own this.
  • Verify Coolify instances and their exposure.
  • Plan and execute upgrades or mitigations.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Coolify?

Coolify is an open-source, self-hosted platform used to manage servers, databases, and applications from a central dashboard. It functions as a control panel for infrastructure, often deployed as a web-based service to facilitate remote management tasks.

What does CVE-2025-66212 mean?

This is a command injection vulnerability, classified as CWE-78. It means the software does not properly sanitize input, specifically proxy configuration filenames, before passing them to the system shell. An attacker can use this flaw to inject and execute their own malicious commands on the underlying server.

How is this vulnerability triggered?

An attacker must have existing authentication with application or service management permissions to trigger the flaw. They exploit it by crafting specific proxy configuration filenames that the system processes insecurely. Note that the vulnerability requires this specific administrative permission level to initiate the command injection.

Is my Coolify instance at risk?

Halo Surface Signal notes that management tools like Coolify are frequently exposed to the internet for remote access, making them an external-facing surface. You should prioritize assessing instances that are reachable over the network, as these provide a direct pathway for authorized users to reach the management interface.

What should I do if I use Coolify?

First, identify all deployed instances of Coolify to determine if they are running an affected version prior to 4.0.0-beta.451. Once identified, your primary action is to update the software to version 4.0.0-beta.451 or later, which resolves the unsafe handling of configuration filenames.

References