Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-64419: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') in coollabsio coolify

0
Critical
VulnerabilityCVE-2025-64419cvecve-2025-64419cwe-77
Published: Mon Jan 05 2026 (01/05/2026, 19:16:44 UTC)
Source: CVE Database V5
Vendor/Project: coollabsio
Product: coolify

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.

AI-Powered Analysis

AILast updated: 01/05/2026, 19:37:30 UTC

Technical Analysis

CVE-2025-64419 is a critical command injection vulnerability identified in Coolify, an open-source, self-hostable platform for managing servers, applications, and databases. The vulnerability stems from improper neutralization of special elements (CWE-77) in parameters extracted from docker-compose.yaml files prior to version 4.0.0-beta.445. Specifically, when a user creates an application using the "docker compose" build pack from a repository controlled by an attacker, unsanitized parameters are passed directly into system commands executed by Coolify. This lack of input validation allows the attacker to inject arbitrary shell commands, which are executed with root privileges on the Coolify host. The vulnerability is remotely exploitable without authentication but requires user interaction in the form of creating an application from a malicious repository. The CVSS v3.1 score of 9.7 reflects the vulnerability's critical nature, with network attack vector, low attack complexity, no privileges required, user interaction required, and complete compromise of confidentiality, integrity, and availability. Although no public exploits have been reported, the risk is high due to the potential for full system takeover. The issue was addressed in version 4.0.0-beta.445 by implementing proper sanitization and validation of docker-compose.yaml parameters before command execution.

Potential Impact

For European organizations, exploitation of this vulnerability could lead to complete compromise of Coolify instances, resulting in unauthorized root-level command execution. This can lead to data breaches, service disruption, lateral movement within networks, and deployment of further malware or ransomware. Organizations relying on Coolify for managing critical infrastructure, applications, or databases face significant operational risks. The attack vector involving malicious repositories could also facilitate supply chain attacks, undermining trust in development workflows. Given the criticality and ease of exploitation, organizations could experience severe confidentiality, integrity, and availability impacts, potentially affecting business continuity and regulatory compliance, especially under GDPR mandates. The threat is particularly relevant for organizations adopting containerized deployments and DevOps automation, which are prevalent in European tech sectors.

Mitigation Recommendations

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.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-03T22:12:51.363Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695c0f8a3839e441758c3632

Added to database: 1/5/2026, 7:22:50 PM

Last enriched: 1/5/2026, 7:37:30 PM

Last updated: 1/8/2026, 1:41:32 PM

Views: 50

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats