CVE-2025-59157: coollabsio coolify · OS Command Injection
Affects coollabsio coolifySource CVE Database V5
Not known to be exploited · CVSS 10.0 Critical : upgrade to 4.0.0-beta.420.7 as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 1.8% chance of exploitation in 30 days – higher than 78% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.0.0-beta.420.7
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade coollabsio coolify to 4.0.0-beta.420.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| coollabsiocoolify | Affected
| Fixed in
|
GitHubcoollabsio/coolifypkg:github/coollabsio/coolifyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
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.
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.