Skip to main content

CVE-2025-34159: CWE-94 Improper Control of Generation of Code ('Code Injection') in coolLabs Technologies Coolify

Critical
VulnerabilityCVE-2025-34159cvecve-2025-34159cwe-94cwe-20
Published: Wed Aug 27 2025 (08/27/2025, 16:47:54 UTC)
Source: CVE Database V5
Vendor/Project: coolLabs Technologies
Product: Coolify

Description

Coolify versions prior to v4.0.0-beta.420.6 are vulnerable to a remote code execution vulnerability in the application deployment workflow. The platform allows authenticated users, with low-level member privileges, to inject arbitrary Docker Compose directives during project creation. By crafting a malicious service definition that mounts the host root filesystem, an attacker can gain full root access to the underlying server.

AI-Powered Analysis

AILast updated: 08/27/2025, 17:18:14 UTC

Technical Analysis

CVE-2025-34159 is a critical remote code execution (RCE) vulnerability affecting Coolify, an application deployment platform developed by coolLabs Technologies. The vulnerability exists in versions prior to v4.0.0-beta.420.6 and stems from improper control over code generation, specifically CWE-94 (Improper Control of Generation of Code). The flaw allows authenticated users with low-level member privileges to inject arbitrary Docker Compose directives during the project creation workflow. By exploiting this, an attacker can craft a malicious service definition that mounts the host's root filesystem inside a container. This effectively grants the attacker full root access to the underlying server hosting the Coolify platform. The vulnerability requires no user interaction beyond authentication and leverages the platform's insufficient validation of Docker Compose configurations. The CVSS 4.0 base score is 9.4 (critical), reflecting the network attack vector, low attack complexity, no required privileges beyond low-level membership, no user interaction, and a high impact on confidentiality, integrity, and availability. Although no public exploits are currently known, the severity and ease of exploitation make this a significant threat. The vulnerability also involves CWE-20 (Improper Input Validation), indicating that the root cause is inadequate sanitization of user-supplied inputs in the deployment workflow. This vulnerability could allow attackers to fully compromise the server, potentially leading to data theft, service disruption, lateral movement within networks, and further compromise of connected systems.

Potential Impact

For European organizations using Coolify for application deployment, this vulnerability poses a severe risk. Successful exploitation can lead to complete server compromise, enabling attackers to access sensitive data, modify or delete applications, disrupt services, and potentially pivot to other internal systems. Given the critical nature of the flaw, organizations relying on Coolify for production workloads could face operational downtime, reputational damage, and regulatory consequences under GDPR if personal data is exposed. The ability for low-privilege authenticated users to escalate privileges to root undermines internal security controls and increases insider threat risks. Additionally, the attack vector being network accessible means that any exposed Coolify instances are at risk. The lack of known exploits in the wild currently provides a window for mitigation, but the critical severity demands immediate action. European sectors with high reliance on containerized deployments and DevOps automation, such as finance, healthcare, and critical infrastructure, are particularly vulnerable to the cascading effects of such a compromise.

Mitigation Recommendations

1. Immediate upgrade to Coolify version v4.0.0-beta.420.6 or later where the vulnerability is patched. If an upgrade is not immediately possible, restrict access to the Coolify deployment interface to trusted internal networks only. 2. Implement strict role-based access controls (RBAC) to limit project creation and deployment privileges only to trusted users. 3. Employ network segmentation and firewall rules to isolate Coolify servers from critical infrastructure and sensitive data stores. 4. Monitor deployment workflows and Docker Compose configurations for anomalous or unauthorized changes, using automated detection tools where possible. 5. Conduct regular audits of user privileges and deployment activities to detect potential misuse. 6. Use container security best practices, such as running containers with least privilege and avoiding mounting host filesystems unless absolutely necessary. 7. Implement host-based intrusion detection systems (HIDS) and endpoint detection and response (EDR) solutions to detect suspicious activities indicative of exploitation attempts. 8. Educate developers and DevOps teams about the risks of injecting untrusted configurations and enforce input validation in deployment pipelines. 9. Maintain up-to-date backups and incident response plans to recover quickly in case of compromise.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulnCheck
Date Reserved
2025-04-15T19:15:22.565Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68af3a3bad5a09ad0064220d

Added to database: 8/27/2025, 5:02:51 PM

Last enriched: 8/27/2025, 5:18:14 PM

Last updated: 8/31/2025, 12:34:23 AM

Views: 18

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

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

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats