Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to Coolify with file-storage rights
-
DeliveryCreate file volume with crafted mount path
-
ExploitInject shell metacharacters in fs_path/parent_dir
-
ExecutionsaveStorageOnServer runs unescaped command
-
PersistExecute arbitrary commands on host
-
ImpactCompromise managed server
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated Coolify account (PR:L) that has permission to add file storage / create a file-mount volume, and the attacker must be able to reach the Coolify web control plane over the network (AV:N). The concrete trigger is supplying a crafted file-mount path (the fs_path / parent_dir values consumed by submitFileStorage and LocalFileVolume::saveStorageOnServer); the payload fires when the storage is saved, with no user interaction needed. The principal limiting factor is that unauthenticated outsiders cannot exploit it - the attacker needs valid credentials and the file-storage privilege - so single-operator instances and those with tightly controlled team membership are much lower risk than multi-tenant or open-registration deployments. |
| Impact | The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) indicates network-reachable, low-complexity exploitation requiring only low privileges and no user interaction, with full confidentiality, integrity, and availability impact - a serious rating for an authenticated flaw. No EPSS score, KEV entry, or SSVC decision data was provided, and no public POC is referenced, so exploitation is currently no public exploit identified at time of analysis; this tempers urgency relative to an actively-exploited bug but does not lower the technical severity. The main gating factor is authentication: an attacker needs a valid Coolify account with permission to add file storage, so multi-tenant or shared Coolify instances face materially higher risk than single-operator deployments. Signals are internally consistent (the PR:L rating matches the description's 'authenticated user' language), so no conflict needs flagging; the chief unknown is the real-world exploitation probability given the absence of EPSS/KEV data. |
| Exploit ScenarioDerived | An attacker who holds (or obtains) a low-privileged Coolify account with permission to add file storage creates a new persistent file volume and supplies a mount path containing shell metacharacters (for example a path with an embedded command substitution or ';' separator). When the storage is saved and saveStorageOnServer builds and runs the unescaped shell command, the injected commands execute on the managed host with the privileges of Coolify's provisioning process. No public POC is referenced, but the low attack complexity (AC:L) and lack of required user interaction make reliable exploitation straightforward once access is obtained. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 06, 2026
Authenticated command injection in Coolify (self-hostable PaaS) before 4.0.0-beta.471 lets any user with rights to add file storage execute arbitrary OS commands on the host. The LocalFileVolume::saveStorageOnServer routine assembles shell commands from user-controlled fs_path and parent_dir values without escaping, and submitFileStorage never validates the file-mount path before volume creation, so injected shell metacharacters run when the storage is saved. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV; risk stems from the low bar (PR:L) and full-compromise impact.
RemediationAI
Vendor-released patch: upgrade Coolify to 4.0.0-beta.471 or later, which adds validation/escaping of the file-mount path before the volume shell command is built (see advisory https://github.com/coollabsio/coolify/security/advisories/GHSA-46hp-7m8g-7622, PR https://github.com/coollabsio/coolify/pull/9176, commit 3fdce06b654fa3b7b4be59c0faaab6b4546c78de). Until the upgrade is applied, restrict who can add file storage by limiting Coolify accounts and team roles to trusted operators only and disabling self-service registration, which reduces the pool of potential attackers at the cost of administrative overhead. Additionally, place the Coolify control-plane UI behind a VPN or IP allowlist so the authenticated attack surface is not broadly network-reachable - this hardens exposure but does not eliminate the flaw for any user who can still reach the file-storage feature, so patching remains the only complete fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Coolify is an open-source, self-hosted platform-as-a-service (an alternative to Heroku/Netlify/Vercel) that provisions and manages servers, applications, and databases, typically via a Laravel/PHP web control plane that issues shell commands over SSH to managed hosts. The flaw is a classic CWE-78 OS Command Injection: the file-storage feature (persistent bind-mount volumes) takes a user-supplied mount path and passes fs_path and parent_dir directly into a constructed shell command string before any validation. Per the CPE cpe:2.3:a:coollabsio:coolify:*, all releases prior to 4.0.0-beta.471 are affected. Because the control plane runs privileged operations to create volumes on the target server, injected command fragments execute in that privileged context rather than being confined to the intended file path.
Know when Coolify gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable web UI (AV:N) with a low-privileged authenticated account able to add file storage (PR:L), no interaction, and command injection yielding full host compromise (C/I/A:H).
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.471, LocalFileVolume::saveStorageOnServer builds shell commands using unescaped fs_path and parent_dir values before validation, and submitFileStorage does not validate the user-controlled file-mount path before creating a volume, allowing an authenticated user who can add file storage to execute commands when the storage is saved. This issue is fixed in version 4.0.0-beta.471.
Executive ViewAI
Coolify platform deployments face critical host compromise risk through a low-privilege command injection vulnerability in file storage features, affecting any organization that grants multi-tenant or non-administrator users access to storage configuration. A currently-unpatched flaw allows attackers to escalate from routine storage setup to complete server control, with no available vendor fix at time of analysis. Organizations must immediately restrict storage privileges or prepare for emergency mitigation pending vendor patches.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict file storage configuration to administrative users only via role-based access controls; (2) Run Coolify in isolated containers with minimal host-level privileges and restricted syscalls; (3) Implement network segmentation to limit lateral movement if container is compromised; (4) Enable comprehensive audit logging of all file storage operations and configuration changes; (5) Disable file storage feature entirely if not required for business operations.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
Cross-team authorization bypass in Coolify (open-source self-hosted PaaS) before 4.0.0-beta.474 allows an authenticated,
Coolify versions prior to v4.0.0-beta.420.7 are vulnerable to a remote code execution vulnerability in the project deplo
Coolify versions prior to v4.0.0-beta.420.6 are vulnerable to a remote code execution vulnerability in the application d
Command injection in Coolify up to and including v4.0.0-beta.434 lets any authenticated low-privileged 'member' execute
Remote code execution on the host OS is possible through Coolify's application deployment workflow prior to version 4.0.
Authenticated command injection in Coolify's PostgreSQL initialization-script filename handling allows users with applic
Coolify versions prior to 4.0.0-beta.451 pass user-supplied database names unsanitized into shell commands executed via
Authenticated Coolify users who hold application or service management permissions can execute arbitrary commands as roo
Authenticated command injection in Coolify before 4.0.0-beta.451 lets users with application or service management permi
Stored cross-site scripting in Coolify versions up to and including v4.0.0-beta.420.6 lets an authenticated low-privileg
Authenticated OS command injection in Coolify before 4.0.0-beta.471 lets any user holding destination management permiss
Authenticated remote code execution in Coolify (self-hosted PaaS) before 4.0.0-beta.470 lets a low-privileged authentica
EUVD-2026-41952
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB