Coolify CVE-2025-59156

Exploitation requires an authenticated low-privileged member/team account on a Coolify instance running a version prior to 4.0.0-beta.420.7 (PR:L). The concrete prerequisite is the ability to define or modify a service's Docker Compose configuration during project creation or update, where the deployment workflow does not neutralize attacker-supplied Compose directives - specifically volume/bind-mount directives that map the host filesystem into a container. No user interaction (UI:N) and no non-default feature toggle is required beyond normal deployment functionality. The primary limiting factor is that the attacker must already possess member-level access, so single-user or fully-trusted-team instances face lower practical risk than multi-tenant instances that grant project-creation rights to semi-trusted users.

This is a genuine high-priority issue, not merely a high-CVSS paper tiger. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) describes network-reachable, low-complexity exploitation requiring only a low-privileged Coolify member account, and the full CIA impact on both the vulnerable system (VC:H/VI:H/VA:H) and subsequent systems (SC:H/SI:H/SA:H) reflects a container-to-host escape that yields root on the underlying host OS. The scope-changing subsequent-system impact is well justified because the attacker breaks out of container isolation onto the host. Critically, a POC/exploit is flagged as publicly available and the advisory itself is tagged as an exploit reference, which materially raises real-world risk. The main tempering signals are EPSS (0.42%, 62th percentile - modest, indicating no observed mass-exploitation yet) and the absence of a CISA KEV listing, so exploitation is 'publicly available exploit code exists' rather than 'confirmed actively exploited.' The one meaningful gate is PR:L: the attacker must already hold a low-privileged member account on a multi-tenant Coolify instance, so exposure concentrates on instances that hand out member/team access to semi-trusted users. No signals conflict; CVSS network vector, description, and CWE-78 are mutually consistent.

A low-privileged member of a shared Coolify instance creates or edits a project and supplies a malicious Docker Compose definition that mounts the host filesystem (e.g. a bind mount of '/' or '/etc') into a service. When Coolify deploys the application, the attacker-controlled service executes commands against the mounted host paths, escaping container isolation to run commands as root on the host OS. A public POC/exploit is available per the GitHub Security Advisory, lowering the skill barrier for this low-complexity, network-reachable attack.