External risk intelligence

Coolify Database Import Command Injection

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2025-66210

Coolify is a management platform for applications and databases often exposed as an administrative web interface. While requiring authentication, it functions as a centralized gateway for infrastructure management, making the web-based surface a common point of network interaction in typical deployments where administrators manage environments from diverse locations.

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 vulnerability exists in Coolify's database import functionality that could allow authenticated users to execute commands on managed servers. This issue affects versions prior to 4.0.0-beta.451, and the primary concern is to confirm if this technology is in use and if so, to verify exposure.

  • Authenticated users can run commands as root.
  • It impacts server management tools used by the organization.
  • Confirm relevance and exposure for affected systems.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by leveraging their existing authenticated access to the Coolify application. Once authenticated with sufficient permissions to manage applications or services, they can craft a malicious database name during an import operation. This specially designed name will then be executed as a command on the server, allowing the attacker to run arbitrary code with root privileges.

  • Authenticated access to application management.
  • Malicious database name in import function.
  • Arbitrary command execution as root.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability in Coolify's database import feature could allow an authenticated user with management permissions to execute arbitrary commands as root on the server. This is possible because database names are inserted directly into shell commands without proper validation, potentially leading to unauthorized system access and control.

  • Managed server root access.
  • Unsanitized database names in commands.
  • Complete server compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

Coolify's self-hosted nature means that application or platform owners are likely responsible for managing its security. The first step is to identify all instances of Coolify, confirm their accessibility and criticality, and then assign ownership for remediation.

  • Application or platform owners should investigate.
  • Verify Coolify's network exposure and criticality.
  • Plan and execute remediation based on risk.

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 comprehensive control plane for deploying and monitoring infrastructure.

What does CVE-2025-66210 mean for Coolify?

This CVE identifies a command injection vulnerability (CWE-78). It occurs because the software fails to sanitize database names during import operations, allowing those names to be processed as shell commands with root privileges.

How can an attacker trigger this vulnerability?

An attacker needs existing authenticated access with application or service management permissions. The bug is triggered when a malicious string is provided in the database name field during an import; standard operations without such input do not trigger the flaw.

Why should I care about this as an administrator?

According to Halo Surface Signal, Coolify is often exposed as an administrative web interface, making it a critical gateway. Since the flaw leads to full remote code execution as root, any internet-facing instance is at high risk.

What is the first step to fix this?

Identify all active Coolify instances in your environment. Once found, verify if they are running a version prior to 4.0.0-beta.451 and prioritize updating them to a patched release to remove the underlying command injection weakness.

References