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-59157: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in coollabsio coolify

0
Critical
VulnerabilityCVE-2025-59157cvecve-2025-59157cwe-78
Published: Mon Jan 05 2026 (01/05/2026, 17:41:29 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.420.7, the Git Repository field during project creation is vulnerable to command injection. User input is not properly sanitized, allowing attackers to inject arbitrary shell commands that execute on the underlying server during the deployment workflow. A regular member user can exploit this vulnerability. Version 4.0.0-beta.420.7 contains a patch for the issue.

AI-Powered Analysis

AILast updated: 01/05/2026, 18:07:25 UTC

Technical Analysis

CVE-2025-59157 is an OS command injection vulnerability categorized under CWE-78 affecting the Coolify platform by coollabsio, an open-source, self-hostable tool for managing servers, applications, and databases. The vulnerability arises from improper neutralization of special elements in the Git Repository input field during project creation. Specifically, user-supplied input is not sanitized before being incorporated into shell commands executed during the deployment workflow. This flaw allows an attacker with regular member privileges to inject arbitrary shell commands that execute with the permissions of the Coolify server process. The vulnerability affects all versions prior to 4.0.0-beta.420.7, which contains a patch that properly sanitizes input to prevent command injection. The CVSS v3.1 base score is 10.0, reflecting the vulnerability's network attack vector (AV:N), low attack complexity (AC:L), requiring privileges (PR:L) but no user interaction (UI:N), with scope changed (S:C), and high impact on confidentiality (C:H), integrity (I:H), and availability (A:H). Exploitation can lead to full system compromise, data theft, service disruption, and lateral movement within the network. No public exploits have been reported yet, but the vulnerability's nature and severity make it a prime target for attackers once disclosed.

Potential Impact

For European organizations, the impact of CVE-2025-59157 can be severe. Coolify is used to manage critical infrastructure components such as servers, applications, and databases; thus, exploitation can lead to unauthorized access to sensitive data, disruption of business-critical services, and potential lateral movement within internal networks. Confidentiality breaches could expose personal data protected under GDPR, leading to regulatory penalties and reputational damage. Integrity violations could corrupt application deployments or database contents, affecting operational reliability. Availability impacts could cause downtime of essential services, harming business continuity. Organizations using vulnerable versions of Coolify in production environments are at high risk, especially those in sectors like finance, healthcare, and government where data sensitivity and service availability are paramount. The ability for a regular member user to exploit this vulnerability increases the threat surface, as insider threats or compromised accounts could be leveraged without elevated privileges or user interaction.

Mitigation Recommendations

To mitigate CVE-2025-59157, European organizations should immediately upgrade all Coolify instances to version 4.0.0-beta.420.7 or later, where the vulnerability is patched. In addition, implement strict access controls and monitoring on Coolify user accounts, limiting membership privileges to trusted personnel only. Employ network segmentation to isolate Coolify servers from critical infrastructure to reduce lateral movement risk. Enable detailed logging and alerting on deployment workflows to detect anomalous command executions. Conduct regular audits of Coolify configurations and user activities. Where possible, deploy Coolify instances within hardened containers or virtual machines with minimal host permissions to contain potential exploitation impact. Educate users about the risks of injecting untrusted input in deployment configurations. Finally, maintain an incident response plan tailored to handle potential command injection attacks and system compromises.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-09-09T15:23:16.327Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695bfa903839e441756fd458

Added to database: 1/5/2026, 5:53:20 PM

Last enriched: 1/5/2026, 6:07:25 PM

Last updated: 1/8/2026, 2:28:37 PM

Views: 35

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