Coolify
Monthly
OS command injection in Coolify, the open-source self-hostable server/application/database management PaaS, allows an authenticated user with permission to edit application settings (versions prior to 4.0.0-beta.469) to run arbitrary commands on the managed host. The flaw lives in the executeInDocker() helper, which wraps user-controlled values in single quotes without escaping embedded quotes, letting an attacker break out of the quoted shell context during deployments and escape the intended Docker container confinement. No public exploit identified at time of analysis; this is not listed in CISA KEV.
Cross-tenant resource access in Coolify (self-hosted PaaS) before 4.0.0-beta.464 lets an authenticated user of one team clone resources into, and access resources owned by, other teams. The cloneTo() Livewire action in ResourceOperations.php checks authorization on the source resource but resolves destination resources with unscoped Eloquent lookups, breaking multi-tenant isolation. Rated CVSS 9.9 with scope change; no public exploit identified at time of analysis, but a fixing commit and vendor advisory are published.
Improper authorization in Coolify's terminal websocket bootstrap routes lets any low-privileged team member execute arbitrary commands on team-managed servers, because the routes verify only that a request is authenticated but never check whether the caller is authorized to use the terminal. Affecting all Coolify versions prior to 4.0.0-beta.471, this CWE-285 flaw carries a critical 9.9 CVSS score with a scope change, effectively granting shell access to underlying infrastructure from a minimal application role. No public exploit identified at time of analysis, but the low complexity and low privilege bar make it a high-priority patch.
OS command injection in Coolify's self-hosted server/app management platform lets an authenticated user achieve remote code execution on the underlying host via a malicious database import container name. The database import Livewire component passes client-controlled container and server properties into shell commands without locking or validation, so any low-privileged authenticated user can inject arbitrary commands. Rated CVSS 8.8 and fixed in 4.0.0-beta.471; no public exploit identified at time of analysis and it is not listed in CISA KEV.
OS command injection in Coolify (self-hosted server/application/database management platform) versions prior to 4.0.0-beta.471 allows an authenticated low-privileged member to run arbitrary commands as root on managed servers by embedding shell metacharacters in persistent volume names, which are interpolated unescaped into shell commands during volume operations. The CVSS 3.1 score is 8.8 (High) with a network vector requiring only low privileges. No public exploit identified at time of analysis; an upstream fix commit and a tagged patched release exist.
Cross-tenant log disclosure in Coolify (self-hosted PaaS) before 4.0.0-beta.466 lets any authenticated user read application logs belonging to other teams by supplying a victim resource's UUID. The Logs::mount() component resolves resources by UUID alone without verifying the caller's team ownership, breaking the multi-tenant isolation boundary. Rated CVSS 7.7 (CWE-639, IDOR); no public exploit identified at time of analysis and it is not listed in CISA KEV, but the fix is a one-line-class authorization check that is trivially reversible from the public commit.
Command injection in Coolify before 4.0.0-beta.471 lets an authenticated user break out of the pre-deployment and post-deployment command fields and run arbitrary shell statements on the target deployment server. The supplied commands are single-quote escaped but then piped through an SSH heredoc transport that preserves newlines, so newline-delimited injected statements survive escaping and execute during deployment. No public exploit is identified at time of analysis, though the fixing pull request and commit are public and make the root cause easy to reconstruct; CVSS is 8.8 (High).
Account takeover vulnerability in Coolify prior to version 4.0.0-beta.471 allows an attacker to reset a victim’s password to a known value by tricking the victim into visiting a crafted invitation URL. The GET /invitations/{uuid} endpoint could perform a state‑changing password reset when the `reset-password` query parameter was present, using the invitation UUID (which the attacker knows) as the new password. This is a CSRF‑based attack (CWE‑352) with a CVSS base score of 8.0; the flaw is patched in the official release and is not known to be actively exploited.
Authenticated command injection in Coolify (self-hosted server/application/database management platform) before 4.0.0-beta.466 lets a user with access to a server's Sentinel settings embed shell metacharacters in the sentinel_token value, which is passed unsanitized into a shell command and executed on the host the next time Sentinel is restarted (CWE-78). The flaw yields full host command execution with confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; the vendor has released a fixed build (v4.0.0-beta.466) with an available upstream commit.
OS command injection in Coolify (self-hosted server/app management platform) before 4.0.0-beta.471 lets an authenticated user embed shell metacharacters in a LocalPersistentVolume storage name, which is interpolated unescaped into docker volume shell commands and executed on managed servers when the associated resource is deleted. Rated CVSS 8.8 (CWE-78), it yields arbitrary command execution on downstream hosts controlled by the Coolify instance. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the fix is confirmed in release 4.0.0-beta.471.
OS command injection in Coolify's self-hosted server-management platform (all versions prior to 4.0.0-beta.471) lets any authenticated team member execute arbitrary shell commands on any managed remote server. The flaw lives in the Livewire Server\Resources component, whose public startUnmanaged/stopUnmanaged/restartUnmanaged methods take a browser-supplied container ID and interpolate it unescaped into SSH-executed shell commands. No public exploit identified at time of analysis and it is not in CISA KEV, but the trivially low complexity (CVSS 8.8) makes exploitation straightforward for anyone with a team account.
OS command injection in Coolify (self-hosted server/application/database management platform) before 4.0.0-beta.466 lets an authenticated user execute arbitrary commands on the host by supplying log drain secret or environment values that are interpolated into shell commands without proper encoding. Because Coolify orchestrates the underlying host, the injected commands run with the platform's host-level context, effectively yielding host takeover. No public exploit identified at time of analysis; this is not in CISA KEV and no POC is referenced, so risk is driven by the ease of authenticated exploitation rather than confirmed in-the-wild activity.
Privilege escalation via broken authorization in Coolify's self-hosted server/application management platform lets any authenticated low-privilege user reach terminal WebSocket functionality for resources outside their authorized scope, prior to version 4.0.0-beta.471. Because the terminal bootstrap routes skipped the expected authorization middleware, an attacker with a valid account can potentially execute commands on servers and containers they should not control. No public exploit identified at time of analysis, and there is no CISA KEV listing, but the fix is confirmed in release v4.0.0-beta.471.
Path traversal leading to remote code execution in Coolify (self-hosted PaaS) before 4.0.0-beta.474 allows an authenticated user to abuse insufficient filename sanitization in the PostgreSQL initialization-script generator (generate_init_scripts() in app/Actions/Database/StartPostgresql.php) to write files outside the intended directory and execute commands during database init. Any user with sufficient privileges to provision a PostgreSQL resource can escalate to code execution on the Coolify host. No public exploit identified at time of analysis, though the fix commit and security advisory publicly disclose the vulnerable code path.
Command injection in Coolify self-hosted PaaS versions prior to 4.0.0-beta.474 allows an authenticated user to run arbitrary OS commands inside the PostgreSQL database container by supplying malicious postgres_user or postgres_db values that are interpolated into shell-form healthcheck commands (CWE-78). Because the CVSS vector is PR:L/UI:N with full high impact to confidentiality, integrity, and availability, any user able to create or configure a database can achieve container-level code execution. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Privilege escalation to root command execution in Coolify (self-hosted PaaS) prior to 4.0.0-beta.471 lets any authenticated user holding the lowest-privilege team 'member' role run arbitrary OS commands as root on every server Coolify manages. The flaw lives in the GetLogs Livewire component, whose $container public property is unsanitized and lacks the #[Locked] attribute, so any team member can tamper with it over the Livewire wire protocol. There is no public exploit identified at time of analysis and the CVE is not in CISA KEV, but the low authentication barrier and full CIA impact make it high priority for any multi-tenant Coolify deployment.
OS command injection in Coolify (self-hosted server/app/database management platform) versions 4.0.0-beta.471 through 4.0.0-beta.473 lets an authenticated team member run arbitrary shell commands on the underlying host. A regression weakened the SHELL_SAFE_COMMAND_PATTERN allowlist so that ampersands were permitted in custom Docker Compose build, start, and pre/post-deployment command fields, enabling command chaining. The issue is fixed in 4.0.0-beta.474; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
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.
Remote command injection in Coolify (self-hosted PaaS) before 4.0.0-beta.469 lets an authenticated user with application write permissions inject OS commands through deployment-handling fields such as dockerfile_location, achieving arbitrary code execution on the deployment host and exfiltrating secrets via deployment logs. The flaw scores CVSS 9.9 because command injection breaks out of the application context to compromise the underlying server (scope change), exposing environment variables and other applications' secrets. No public exploit has been identified at time of analysis, but the fix is available in tagged release v4.0.0-beta.469.
Authenticated command injection in Coolify's CA Certificate management feature (all versions prior to 4.0.0-beta.464) lets any logged-in user inject arbitrary OS commands that execute as the configured SSH user on a managed server. Because Coolify requires that SSH user to be root or a docker-group member, successful exploitation yields full compromise of the managed host and every Docker container it runs. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, but the low attack complexity and minimal privilege requirement make it a high-priority patch for any multi-user Coolify instance.
Cross-team data exposure in Coolify (self-hostable PaaS) before 4.0.0-beta.471 allows any authenticated user to read servers and projects owned by other teams by supplying their object IDs directly. The flaw is a broken object-level authorization (IDOR) where lookups are never scoped to the requester's team, breaching the multi-tenant boundary. No public exploit identified at time of analysis, and the issue is resolved in 4.0.0-beta.471.
Authenticated OS command injection in Coolify before 4.0.0-beta.471 lets any user holding destination management permissions execute arbitrary commands as root on managed servers. The 'network' parameter in the Destination Network Management feature is passed unsanitized into shell commands, yielding full root-level remote code execution on the host. No public exploit identified at time of analysis; the issue is fixed in 4.0.0-beta.471.
Authenticated remote code execution in Coolify (self-hosted PaaS) before 4.0.0-beta.470 lets a low-privileged authenticated user run arbitrary commands on the deployment host. The flaw is an OS command injection in the Nixpacks build pack: the user-supplied install_command build parameter is concatenated unsanitized into a shell command executed during the build phase, allowing escape from the build context to host-level command execution. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV, but the path to abuse is straightforward for any user who can configure a deployment.
Webhook signature forgery in Coolify (self-hosted PaaS) before 4.0.0-beta.474 lets unauthenticated remote attackers trigger arbitrary application deployments. Because the per-application manual_webhook_secret_github field is nullable with no default, newly created applications carry a null HMAC key; PHP's hash_hmac() silently coerces null to an empty string, so the expected X-Hub-Signature-256 becomes a deterministic value any attacker can compute offline. There is no public exploit identified at time of analysis and the flaw is not in CISA KEV, but exploitation is trivial against affected default configurations.
Cross-team authorization bypass in Coolify (open-source self-hosted PaaS) before 4.0.0-beta.474 allows an authenticated, low-privileged member of one team to deploy and manipulate resources belonging to other teams. While the REST API controllers correctly enforce ownership via Server::whereTeamId($teamId), several Livewire web UI components trust attacker-supplied server_id and destination_uuid URL query parameters with no team-ownership check (CWE-639). No public exploit identified at time of analysis, but the CVSS 9.6 rating and trivially manipulable parameters make this a high-priority fix for any multi-tenant Coolify deployment.
Missing authentication in Coolify's GitHub App setup handler (Github::redirect at /webhooks/source/github/redirect) in versions up to and including 4.1.0 allows unauthenticated remote attackers to supply a crafted 'state' value matching an existing GitHub App UUID and cause the application to run the GitHub App manifest conversion flow, overwriting that App's stored client ID, client secret, webhook secret and private key. Publicly available exploit code exists, but exploitation is gated on knowing a valid - typically mid-setup - GitHub App UUID, which the independent assessment treats as raising attack complexity above the vendor's AC:L rating (CVSS:3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N), making this a genuine but moderate-severity credential-overwrite issue rather than a trivially mass-exploitable bypass. No CISA KEV entry or confirmed in-the-wild activity has been reported; the CVE is currently associated only with published proof-of-concept material against the affected endpoint.
Missing authorization in Coolify up to and including 4.1.2 allows remote attackers to perform resource-update operations they are not entitled to, because the CanUpdateResource route-level middleware was shipped with its entire authorization body - the Gate::allows('update', $resource) check and the surrounding resource-resolution logic - commented out, turning it into a no-op pass-through. Any multi-user or multi-team Coolify deployment on 4.1.2 or earlier is exposed across application, database, service, server, environment and project update routes; the vendor's CVSS 4.0 vector rates the flaw PR:N while the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L) indicates a valid authenticated Coolify account is realistically required, since the affected routes sit behind login. Publicly available exploit code exists and upgrading to 4.2.0 fixes the issue; there is no CISA KEV listing, so this is not confirmed active exploitation.
OS command injection in Coolify's database service configuration API allows authenticated administrators to execute arbitrary shell commands within Docker container contexts by embedding shell metacharacters into database credential fields. All Coolify versions prior to 4.0.0-beta.474 are affected, covering deployments managing Redis, KeyDB, Dragonfly, ClickHouse, PostgreSQL, and MySQL services. No public exploit code has been identified at time of analysis, and the CVSS PR:H requirement confines the attack surface to already-privileged admin accounts, positioning this as a post-compromise escalation risk rather than an initial access vector.
Server-Side Request Forgery (SSRF) in Coolify's GitHub App integration exposes internal network services and cloud metadata endpoints to authenticated low-privilege users. Versions prior to 4.0.0-beta.471 allow any authenticated user to set the GithubApp api_url field to an arbitrary URL - including RFC 1918 private addresses or cloud instance metadata endpoints like 169.254.169.254 - which Coolify then fetches server-side without restriction. No public exploit identified at time of analysis, but the attack pattern is well understood and particularly dangerous in cloud-hosted deployments where metadata endpoints may expose IAM credentials.
Server-Side Request Forgery (SSRF) in Coolify prior to v4.0.0-beta.474 enables an authenticated user holding storage management permissions to coerce the application server into issuing HTTP requests to arbitrary internal addresses, including cloud instance metadata services. The vulnerable code path is Coolify's S3 storage endpoint testConnection() function, which blindly fetches the caller-supplied URL after only superficial format validation. No public exploit or CISA KEV listing exists at time of analysis, but cloud-hosted deployments face elevated risk because successful exploitation can expose cloud provider credentials via metadata endpoints such as AWS IMDSv1.
Command injection in Coolify's DatabaseBackupJob allows authenticated users holding database management permissions to execute arbitrary OS commands on managed servers by embedding shell metacharacters in database credentials or MongoDB collection exclusion names. All Coolify releases prior to 4.0.0-beta.471 are affected. No public exploit code has been identified at time of analysis and the vulnerability is absent from CISA KEV; however, the practical impact substantially exceeds the official CVSS 3.3 Low rating because successful exploitation grants attacker-controlled shell execution on production infrastructure managed by the platform.
Coolify's database backup restore file upload endpoint accepts uploads without enforcing any file type or size constraints, enabling an authenticated user to degrade service availability by uploading oversized or unexpected files. All releases prior to 4.0.0-beta.474 are affected per CPE cpe:2.3:a:coollabsio:coolify. No public exploit code exists and the vulnerability is not listed in CISA KEV; with a CVSS score of 3.1 and availability-only impact, this represents a low-priority issue for most operators, especially given the authenticated access requirement.
Password reset poisoning in Coolify prior to 4.0.0-beta.471 enables unauthenticated account takeover by injecting a forged X-Forwarded-Host header during a password reset request. Two compounding middleware failures make this possible: TrustProxies trusts all proxy sources unconditionally, and TrustHosts is rendered inoperable by a circular caching dependency, meaning the Host header is never validated. The reset URL is generated from the spoofed request host, so the victim's reset token is delivered to an attacker-controlled domain. No public exploit is identified at time of analysis, but the attack is low-friction and the fix is confirmed in version 4.0.0-beta.471.
Sanctum API tokens in Coolify never expire prior to v4.0.0-beta.474, meaning any token that is leaked or stolen remains permanently valid until an administrator manually revokes it. This affects the self-hosted server, application, and database management platform across all versions below 4.0.0-beta.474. An attacker who obtains a valid API token via secondary means retains indefinite read access to the Coolify API without natural time-bounded expiry as a safeguard. No public exploit has been identified at time of analysis, and the low CVSS score of 3.1 reflects the constrained real-world impact.
Insecure Direct Object Reference (IDOR) in Coolify's ActivityMonitor Livewire component allows any authenticated user to enumerate and read activity records belonging to other teams, including full SSH process command outputs that may contain secrets, credentials, and infrastructure configuration details. Affected are all Coolify self-hosted deployments prior to version 4.0.0-beta.471. No special privileges beyond a valid user account are required, and auto-incrementing integer activity IDs make enumeration trivial. No public exploit code has been identified at time of analysis and this CVE is not in CISA KEV, but the low attack complexity and sensitive data exposure make this a meaningful risk for multi-tenant Coolify deployments.
Command injection in Coolify's MongoDB backup handler (versions 4.0.0-beta.451 through 4.0.0-beta.470) allows a highly privileged attacker who controls backup configuration to inject OS-level shell commands via unsanitized metacharacters in MongoDB collection names. The attack requires an already-administrative account capable of modifying backup inputs, substantially limiting the realistic threat surface. No public exploit has been identified and this vulnerability is not listed in CISA KEV; the vendor released a fix in v4.0.0-beta.471.
OS command injection in Coolify's settings module allows a highly privileged attacker in a development environment to execute arbitrary shell commands on the host server by injecting metacharacters into the dev_helper_version field, which is passed unsanitized into a Docker build command. All Coolify releases prior to 4.0.0-beta.474 are affected. No public exploit code exists and no CISA KEV listing has been issued; the provided CVSS score of 3.8 (Low) accurately reflects the highly constrained exploitation prerequisites, though the underlying command injection class warrants upgrade regardless.
Unauthenticated access to Coolify's POST /api/feedback endpoint allows any remote attacker to forward arbitrary content directly to the operator's configured Discord webhook, enabling spam flooding, content injection, and webhook rate-limit abuse. All self-hosted Coolify instances prior to 4.0.0-beta.474 are affected, with CVSS AV:N/AC:L/PR:N/UI:N confirming zero-barrier network exploitation. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, but the trivial exploit conditions (plain unauthenticated HTTP POST) make automated abuse straightforward.
Missing authorization in Coolify's Settings/Updates Livewire component allows any authenticated non-admin user to access the Updates settings page and modify auto-update behavior or trigger update checks. Affected versions span all releases prior to 4.0.0-beta.471 of the self-hosted server management platform. No public exploit code or CISA KEV listing exists at time of analysis, but the network-accessible nature and low authentication bar (any valid account) make this a meaningful integrity risk in multi-tenant or shared Coolify deployments.
Incorrect authorization in Coolify's API layer allows any holder of a read-scoped API token to invoke mutating validation endpoints - including cloud token validation and server validation - that should require write-level privileges. All Coolify deployments prior to version 4.0.0-beta.466 are affected. No public exploit or active exploitation has been identified at time of analysis, but the low attack complexity and network accessibility via API make this straightforward to abuse for any user who has been issued even a minimal API token.
Information disclosure in Coolify allows any authenticated API user to enumerate domain names (FQDNs) of applications belonging to other teams. The issue exists in versions before 4.0.0-beta.464 and is fixed in that release. No active exploitation or public exploit code has been identified, and EPSS predicts very low exploitation probability.
Command injection in Coolify prior to 4.0.0-beta.464 allows authenticated administrators to escape the Docker container and execute arbitrary commands on the host server. The vulnerability originates from the executeInDocker() helper that wraps commands in bash -c '{$command}' without escaping single quotes, enabling injection via user-controlled Docker compose fields. A proof-of-concept exploit exists, but no active exploitation is reported (EPSS 0.22%, low risk).
Authenticated users can access deployment details of any team in Coolify prior to version 4.0.0-beta.464, bypassing team-based authorization. The vulnerability exposes sensitive deployment configuration and metadata, requiring only low-privilege authentication and no user interaction. A public proof-of-concept exists, but EPSS indicates a low probability of widespread exploitation (0.21%).
Information disclosure in Coolify API allows authenticated users to retrieve deployment records from arbitrary teams prior to version 4.0.0-beta.464. By supplying a valid deployment UUID to the /api/v1/deployments/{uuid} endpoint, any low-privileged authenticated user can read deployment details belonging to other teams, violating team isolation. This vulnerability has a CVSS score of 5.0, public exploit code exists, and no active exploitation has been confirmed (CISA KEV absent), with a low EPSS probability of 0.16%.
Coolify's GitLab webhook endpoint leaks its secret token through a timing side-channel, enabling unauthenticated network attackers to reconstruct the token incrementally by measuring HTTP response time differences. All self-hosted Coolify instances prior to 4.0.0-beta.461 with GitLab webhook integrations configured are affected. Once the secret is recovered, an attacker can forge arbitrary GitLab webhook events and potentially trigger unauthorized deployments. No public exploit or active exploitation has been identified at time of analysis; the CVSS-assigned AC:H correctly reflects the practical difficulty of conducting reliable timing measurements over real-world networks.
OS command injection in Coolify 4.0.0's Image Name Handler allows authenticated remote attackers to execute arbitrary operating system commands by manipulating image name inputs. Coolify is a self-hosted PaaS that orchestrates Docker deployments, making server-side command injection in its image handling pipeline particularly high-impact - the platform typically operates with Docker daemon privileges. Publicly available exploit code exists (CVSS 4.0 E:P, corroborated by a GitHub PoC writeup); no public confirmation of active exploitation is present, and no vendor response to the coordinated disclosure was received.
Account takeover in Coolify v4.0.0-beta.434 and earlier is possible because the self-hosted platform's password-reset flow builds the reset link from the attacker-controllable HTTP Host header, so a remote unauthenticated attacker can trigger a reset for a known victim email and have the resulting email point at a server they control - capturing the reset token when the victim clicks the link and using it to set a new password. No authentication is required (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N), but exploitation is per-victim and strictly dependent on the target clicking the poisoned link; instances that pin a canonical application URL or enforce a trusted Host header at a reverse proxy are not exploitable. Publicly available exploit code exists, but there is no confirmed active exploitation in the wild (EPSS is only 0.05%, ~15th percentile) and no vendor-released patch is confirmed as of publication.
Command injection in Coolify up to and including v4.0.0-beta.434 lets any authenticated low-privileged 'member' execute arbitrary system commands as root on the Coolify instance by supplying shell metacharacters in a resource's git source input field. Remote exploitation requires no admin rights and no user interaction, so any team-shared or multi-tenant deployment that lets members create or edit resources is exposed, and this is a genuine high-priority issue rather than a CVSS-inflated one. Publicly available exploit code exists (NVD exploit references including a GitHub security advisory and an accompanying demonstration file), while the EPSS score remains low at 0.47% (64th percentile) and no fixed version was confirmed at the time of publication.
Privilege escalation in Coolify (self-hostable server/application/database management platform) up to and including v4.0.0-beta.434 allows a low-privileged 'member' account to view and redeem administrator invitation links, letting the attacker log in with administrator privileges before the legitimate recipient accepts the invite. Exploitation is not unauthenticated - the CVSS 4.0 vector (PR:L) and our independent CVSS 3.1 assessment (AV:N/AC:H/PR:L/UI:N) confirm the attacker must already hold a valid member account on a shared, multi-user instance, and must win a timing window (AT:P) in which an admin invitation is outstanding and still unclaimed. Publicly available exploit code exists, though there is no confirmed active exploitation (not in CISA KEV) and EPSS is low at 0.05% (16th percentile); real-world risk is therefore moderate and bounded by the member foothold and race-condition prerequisites.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. In Coolify vstarting with version 4.0.0-beta.434, the /login endpoint advertises a rate limit of 5 requests but can be trivially bypassed by rotating the X-Forwarded-For header. [CVSS 4.3 MEDIUM]
Privilege escalation in Coolify (coollabs) up to and including v4.0.0-beta.434 lets an authenticated low-privileged member gain full administrator control by abusing the team invitation workflow: the first attempt to invite an administrator-level user returns an error, but re-submitting the same invite succeeds and creates the higher-privileged account. The attacker can then initiate a password reset against that newly created admin identity and log in as an administrator, achieving complete compromise of the instance (high confidentiality, integrity, and availability impact). Exploitation requires a valid low-privileged member account and no victim interaction; publicly available exploit code exists (GitHub advisory GHSA-4p6r-m39m-9cm9), there is no confirmation of active exploitation, and EPSS is low at roughly 0.04% (13th percentile).
Coolify instances running v4.0.0-beta.434 or earlier expose the root user's private SSH key to any authenticated low-privilege user, turning a limited application account into full root access on the underlying host (C:H/I:H/A:H, CVSS 8.8). The vulnerable path requires an existing low-privilege Coolify account (PR:L per the vector) and then yields the root SSH key with no further interaction, though escalating to root also requires network reachability of the host's SSH service. Publicly available exploit code exists and the EPSS score is low (0.05%, 16th percentile), and as of publication it is unclear whether a vendor patch is available, so multi-user or multi-tenant Coolify deployments are the primary risk population while single-operator installations with no additional low-privilege users have effectively no exposed attacker population.
Command injection in Coolify instances running versions prior to 4.0.0-beta.445 lets an attacker who controls the Git repository used to create an application execute arbitrary commands as root on the Coolify host. The flaw is triggered when a victim user creates or deploys an application using the 'docker compose' build pack from an attacker-supplied repository whose docker-compose.yaml supplies unsanitized parameters that are later interpolated into shell commands executed by Coolify. Publicly available exploit code exists, and the CVSS vector (AV:N/AC:L/PR:N/UI:R) confirms a remote, unauthenticated attack path that nevertheless requires the victim to initiate the build, so real-world exploitation is gated by social engineering rather than direct remote access; EPSS is low at roughly 0.09% (26th percentile). A vendor patch is available in version 4.0.0-beta.445.
Coolify versions up to 4.0.0 contains a vulnerability that allows attackers to a malicious actor to perform an unauthorized email address change on behalf of t (CVSS 5.7).
Stored cross-site scripting in Coolify versions up to and including v4.0.0-beta.420.6 lets an authenticated low-privilege member create a project whose name contains JavaScript; the payload runs in an administrator's browser when the admin later opens the delete flow for that project or an associated resource. Publicly available exploit code exists, but EPSS is low (0.05%, 15th percentile) and no CISA KEV active-exploitation signal was provided, so practical priority is moderate despite the vendor's CVSS 4.0 base of 9.4; the independent CVSS 3.1 assessment is AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, reflecting the need for a member account and administrator interaction. Exposure mainly affects multi-tenant or team deployments where untrusted members can create projects, while single-admin self-hosted instances without untrusted members are effectively not exposed.
Command injection in Coolify's Git Repository field during project creation allows an authenticated member account to run arbitrary shell commands on the self-hosted Coolify server when the project's deployment workflow executes. All releases prior to 4.0.0-beta.420.7 are affected, and publicly available exploit code exists, so member-restricted instances that permit untrusted or self-registered users carry real risk. Exploitation is access-gated rather than anonymous: the CVSS vector (PR:L, AV:N, UI:N) confirms a low-privileged authenticated attacker is required, and the EPSS score of 0.26% (49th percentile) indicates low observed exploitation activity with no CISA KEV listing at time of analysis.
Remote code execution on the host OS is possible through Coolify's application deployment workflow prior to version 4.0.0-beta.420.7, where an authenticated member-level user can inject malicious Docker Compose directives-such as bind mounts of the host filesystem-during project creation or updates. This bypasses container isolation and yields root-level command execution on the Coolify host. Publicly available exploit code exists, and while the EPSS score is modest at 0.42% (62nd percentile), the severity is high because exploitation requires only a low-privileged team account and no user interaction; a vendor patch is available.
Authenticated Coolify users who hold application or service management permissions can execute arbitrary commands as root on managed servers by supplying a crafted file_storage_directory_source value in the File Storage Directory Mount Path feature. The parameter reaches shell command construction without sanitization, so shell metacharacters enable full host compromise; no victim interaction is required, but the attacker must already be authenticated with management rights. Publicly available exploit code exists, the vendor fixed the flaw in 4.0.0-beta.451, and EPSS is low at 0.20%, suggesting limited observed exploitation at time of analysis.
Authenticated command injection in Coolify before 4.0.0-beta.451 lets users with application or service management permissions execute arbitrary commands as root on managed servers by supplying a Dynamic Proxy Configuration filename containing shell metacharacters. Exploitation requires a valid low-privilege Coolify account and no user interaction; unauthenticated or read-only users cannot trigger it directly. Publicly available exploit code exists, but EPSS is only 0.20% (41st percentile), and risk is concentrated in multi-user or shared deployments where service-management roles are broadly granted or an operator account is compromised.
Authenticated command injection in Coolify's PostgreSQL initialization-script filename handling allows users with application or service management permissions to execute arbitrary commands as root on managed servers. All Coolify 4.0.0 beta builds prior to beta.451 are affected, publicly available exploit code exists, and the upstream fix also covers database names used in backup configuration. EPSS is low at 0.41% (61st percentile), but the impact is severe for multi-user or multi-tenant deployments where lower-trust operators hold management rights.
Coolify versions prior to 4.0.0-beta.451 pass user-supplied database names unsanitized into shell commands executed via docker exec on managed servers, allowing an authenticated user with application/service management permissions to run arbitrary commands as root. Exploitation is remote but requires a valid management-capable account (PR:L), so the realistic exposure is multi-user, multi-tenant, or credential-compromise scenarios rather than anonymous mass exploitation. Publicly available exploit code exists and EPSS is modest at 0.41% (61st percentile); no confirmed active exploitation (CISA KEV) at time of analysis.
Authenticated command injection in Coolify before 4.0.0-beta.451 allows users with application or service management permissions to execute arbitrary commands as root on managed servers through the Database Backup feature. The flaw is caused by database names being inserted into shell commands without sanitization when backup jobs invoke mongodump, pg_dump, mysqldump, and mariadb-dump via docker exec; publicly available exploit code exists and EPSS is 0.20% (42nd percentile). The vendor-released patch is version 4.0.0-beta.451, and no CISA KEV confirmation was provided in the available data.
Coolify versions prior to v4.0.0-beta.420.7 are vulnerable to a remote code execution vulnerability in the project deployment workflow. Rated critical severity (CVSS 9.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Coolify versions prior to v4.0.0-beta.420.6 are vulnerable to a remote code execution vulnerability in the application deployment workflow. Rated critical severity (CVSS 9.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Coolify versions prior to v4.0.0-beta.420.6 are vulnerable to a stored cross-site scripting (XSS) attack in the project creation workflow. Rated critical severity (CVSS 9.4), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated low severity (CVSS 1.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated critical severity (CVSS 10.0), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated medium severity (CVSS 5.7), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated critical severity (CVSS 10.0), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated medium severity (CVSS 4.7), this vulnerability is low attack complexity. No vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated high severity (CVSS 8.5), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated high severity (CVSS 8.5), this vulnerability is low attack complexity. Public exploit code available.
OS command injection in Coolify, the open-source self-hostable server/application/database management PaaS, allows an authenticated user with permission to edit application settings (versions prior to 4.0.0-beta.469) to run arbitrary commands on the managed host. The flaw lives in the executeInDocker() helper, which wraps user-controlled values in single quotes without escaping embedded quotes, letting an attacker break out of the quoted shell context during deployments and escape the intended Docker container confinement. No public exploit identified at time of analysis; this is not listed in CISA KEV.
Cross-tenant resource access in Coolify (self-hosted PaaS) before 4.0.0-beta.464 lets an authenticated user of one team clone resources into, and access resources owned by, other teams. The cloneTo() Livewire action in ResourceOperations.php checks authorization on the source resource but resolves destination resources with unscoped Eloquent lookups, breaking multi-tenant isolation. Rated CVSS 9.9 with scope change; no public exploit identified at time of analysis, but a fixing commit and vendor advisory are published.
Improper authorization in Coolify's terminal websocket bootstrap routes lets any low-privileged team member execute arbitrary commands on team-managed servers, because the routes verify only that a request is authenticated but never check whether the caller is authorized to use the terminal. Affecting all Coolify versions prior to 4.0.0-beta.471, this CWE-285 flaw carries a critical 9.9 CVSS score with a scope change, effectively granting shell access to underlying infrastructure from a minimal application role. No public exploit identified at time of analysis, but the low complexity and low privilege bar make it a high-priority patch.
OS command injection in Coolify's self-hosted server/app management platform lets an authenticated user achieve remote code execution on the underlying host via a malicious database import container name. The database import Livewire component passes client-controlled container and server properties into shell commands without locking or validation, so any low-privileged authenticated user can inject arbitrary commands. Rated CVSS 8.8 and fixed in 4.0.0-beta.471; no public exploit identified at time of analysis and it is not listed in CISA KEV.
OS command injection in Coolify (self-hosted server/application/database management platform) versions prior to 4.0.0-beta.471 allows an authenticated low-privileged member to run arbitrary commands as root on managed servers by embedding shell metacharacters in persistent volume names, which are interpolated unescaped into shell commands during volume operations. The CVSS 3.1 score is 8.8 (High) with a network vector requiring only low privileges. No public exploit identified at time of analysis; an upstream fix commit and a tagged patched release exist.
Cross-tenant log disclosure in Coolify (self-hosted PaaS) before 4.0.0-beta.466 lets any authenticated user read application logs belonging to other teams by supplying a victim resource's UUID. The Logs::mount() component resolves resources by UUID alone without verifying the caller's team ownership, breaking the multi-tenant isolation boundary. Rated CVSS 7.7 (CWE-639, IDOR); no public exploit identified at time of analysis and it is not listed in CISA KEV, but the fix is a one-line-class authorization check that is trivially reversible from the public commit.
Command injection in Coolify before 4.0.0-beta.471 lets an authenticated user break out of the pre-deployment and post-deployment command fields and run arbitrary shell statements on the target deployment server. The supplied commands are single-quote escaped but then piped through an SSH heredoc transport that preserves newlines, so newline-delimited injected statements survive escaping and execute during deployment. No public exploit is identified at time of analysis, though the fixing pull request and commit are public and make the root cause easy to reconstruct; CVSS is 8.8 (High).
Account takeover vulnerability in Coolify prior to version 4.0.0-beta.471 allows an attacker to reset a victim’s password to a known value by tricking the victim into visiting a crafted invitation URL. The GET /invitations/{uuid} endpoint could perform a state‑changing password reset when the `reset-password` query parameter was present, using the invitation UUID (which the attacker knows) as the new password. This is a CSRF‑based attack (CWE‑352) with a CVSS base score of 8.0; the flaw is patched in the official release and is not known to be actively exploited.
Authenticated command injection in Coolify (self-hosted server/application/database management platform) before 4.0.0-beta.466 lets a user with access to a server's Sentinel settings embed shell metacharacters in the sentinel_token value, which is passed unsanitized into a shell command and executed on the host the next time Sentinel is restarted (CWE-78). The flaw yields full host command execution with confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; the vendor has released a fixed build (v4.0.0-beta.466) with an available upstream commit.
OS command injection in Coolify (self-hosted server/app management platform) before 4.0.0-beta.471 lets an authenticated user embed shell metacharacters in a LocalPersistentVolume storage name, which is interpolated unescaped into docker volume shell commands and executed on managed servers when the associated resource is deleted. Rated CVSS 8.8 (CWE-78), it yields arbitrary command execution on downstream hosts controlled by the Coolify instance. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, but the fix is confirmed in release 4.0.0-beta.471.
OS command injection in Coolify's self-hosted server-management platform (all versions prior to 4.0.0-beta.471) lets any authenticated team member execute arbitrary shell commands on any managed remote server. The flaw lives in the Livewire Server\Resources component, whose public startUnmanaged/stopUnmanaged/restartUnmanaged methods take a browser-supplied container ID and interpolate it unescaped into SSH-executed shell commands. No public exploit identified at time of analysis and it is not in CISA KEV, but the trivially low complexity (CVSS 8.8) makes exploitation straightforward for anyone with a team account.
OS command injection in Coolify (self-hosted server/application/database management platform) before 4.0.0-beta.466 lets an authenticated user execute arbitrary commands on the host by supplying log drain secret or environment values that are interpolated into shell commands without proper encoding. Because Coolify orchestrates the underlying host, the injected commands run with the platform's host-level context, effectively yielding host takeover. No public exploit identified at time of analysis; this is not in CISA KEV and no POC is referenced, so risk is driven by the ease of authenticated exploitation rather than confirmed in-the-wild activity.
Privilege escalation via broken authorization in Coolify's self-hosted server/application management platform lets any authenticated low-privilege user reach terminal WebSocket functionality for resources outside their authorized scope, prior to version 4.0.0-beta.471. Because the terminal bootstrap routes skipped the expected authorization middleware, an attacker with a valid account can potentially execute commands on servers and containers they should not control. No public exploit identified at time of analysis, and there is no CISA KEV listing, but the fix is confirmed in release v4.0.0-beta.471.
Path traversal leading to remote code execution in Coolify (self-hosted PaaS) before 4.0.0-beta.474 allows an authenticated user to abuse insufficient filename sanitization in the PostgreSQL initialization-script generator (generate_init_scripts() in app/Actions/Database/StartPostgresql.php) to write files outside the intended directory and execute commands during database init. Any user with sufficient privileges to provision a PostgreSQL resource can escalate to code execution on the Coolify host. No public exploit identified at time of analysis, though the fix commit and security advisory publicly disclose the vulnerable code path.
Command injection in Coolify self-hosted PaaS versions prior to 4.0.0-beta.474 allows an authenticated user to run arbitrary OS commands inside the PostgreSQL database container by supplying malicious postgres_user or postgres_db values that are interpolated into shell-form healthcheck commands (CWE-78). Because the CVSS vector is PR:L/UI:N with full high impact to confidentiality, integrity, and availability, any user able to create or configure a database can achieve container-level code execution. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.
Privilege escalation to root command execution in Coolify (self-hosted PaaS) prior to 4.0.0-beta.471 lets any authenticated user holding the lowest-privilege team 'member' role run arbitrary OS commands as root on every server Coolify manages. The flaw lives in the GetLogs Livewire component, whose $container public property is unsanitized and lacks the #[Locked] attribute, so any team member can tamper with it over the Livewire wire protocol. There is no public exploit identified at time of analysis and the CVE is not in CISA KEV, but the low authentication barrier and full CIA impact make it high priority for any multi-tenant Coolify deployment.
OS command injection in Coolify (self-hosted server/app/database management platform) versions 4.0.0-beta.471 through 4.0.0-beta.473 lets an authenticated team member run arbitrary shell commands on the underlying host. A regression weakened the SHELL_SAFE_COMMAND_PATTERN allowlist so that ampersands were permitted in custom Docker Compose build, start, and pre/post-deployment command fields, enabling command chaining. The issue is fixed in 4.0.0-beta.474; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
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.
Remote command injection in Coolify (self-hosted PaaS) before 4.0.0-beta.469 lets an authenticated user with application write permissions inject OS commands through deployment-handling fields such as dockerfile_location, achieving arbitrary code execution on the deployment host and exfiltrating secrets via deployment logs. The flaw scores CVSS 9.9 because command injection breaks out of the application context to compromise the underlying server (scope change), exposing environment variables and other applications' secrets. No public exploit has been identified at time of analysis, but the fix is available in tagged release v4.0.0-beta.469.
Authenticated command injection in Coolify's CA Certificate management feature (all versions prior to 4.0.0-beta.464) lets any logged-in user inject arbitrary OS commands that execute as the configured SSH user on a managed server. Because Coolify requires that SSH user to be root or a docker-group member, successful exploitation yields full compromise of the managed host and every Docker container it runs. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV, but the low attack complexity and minimal privilege requirement make it a high-priority patch for any multi-user Coolify instance.
Cross-team data exposure in Coolify (self-hostable PaaS) before 4.0.0-beta.471 allows any authenticated user to read servers and projects owned by other teams by supplying their object IDs directly. The flaw is a broken object-level authorization (IDOR) where lookups are never scoped to the requester's team, breaching the multi-tenant boundary. No public exploit identified at time of analysis, and the issue is resolved in 4.0.0-beta.471.
Authenticated OS command injection in Coolify before 4.0.0-beta.471 lets any user holding destination management permissions execute arbitrary commands as root on managed servers. The 'network' parameter in the Destination Network Management feature is passed unsanitized into shell commands, yielding full root-level remote code execution on the host. No public exploit identified at time of analysis; the issue is fixed in 4.0.0-beta.471.
Authenticated remote code execution in Coolify (self-hosted PaaS) before 4.0.0-beta.470 lets a low-privileged authenticated user run arbitrary commands on the deployment host. The flaw is an OS command injection in the Nixpacks build pack: the user-supplied install_command build parameter is concatenated unsanitized into a shell command executed during the build phase, allowing escape from the build context to host-level command execution. There is no public exploit identified at time of analysis, and it is not listed in CISA KEV, but the path to abuse is straightforward for any user who can configure a deployment.
Webhook signature forgery in Coolify (self-hosted PaaS) before 4.0.0-beta.474 lets unauthenticated remote attackers trigger arbitrary application deployments. Because the per-application manual_webhook_secret_github field is nullable with no default, newly created applications carry a null HMAC key; PHP's hash_hmac() silently coerces null to an empty string, so the expected X-Hub-Signature-256 becomes a deterministic value any attacker can compute offline. There is no public exploit identified at time of analysis and the flaw is not in CISA KEV, but exploitation is trivial against affected default configurations.
Cross-team authorization bypass in Coolify (open-source self-hosted PaaS) before 4.0.0-beta.474 allows an authenticated, low-privileged member of one team to deploy and manipulate resources belonging to other teams. While the REST API controllers correctly enforce ownership via Server::whereTeamId($teamId), several Livewire web UI components trust attacker-supplied server_id and destination_uuid URL query parameters with no team-ownership check (CWE-639). No public exploit identified at time of analysis, but the CVSS 9.6 rating and trivially manipulable parameters make this a high-priority fix for any multi-tenant Coolify deployment.
Missing authentication in Coolify's GitHub App setup handler (Github::redirect at /webhooks/source/github/redirect) in versions up to and including 4.1.0 allows unauthenticated remote attackers to supply a crafted 'state' value matching an existing GitHub App UUID and cause the application to run the GitHub App manifest conversion flow, overwriting that App's stored client ID, client secret, webhook secret and private key. Publicly available exploit code exists, but exploitation is gated on knowing a valid - typically mid-setup - GitHub App UUID, which the independent assessment treats as raising attack complexity above the vendor's AC:L rating (CVSS:3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N), making this a genuine but moderate-severity credential-overwrite issue rather than a trivially mass-exploitable bypass. No CISA KEV entry or confirmed in-the-wild activity has been reported; the CVE is currently associated only with published proof-of-concept material against the affected endpoint.
Missing authorization in Coolify up to and including 4.1.2 allows remote attackers to perform resource-update operations they are not entitled to, because the CanUpdateResource route-level middleware was shipped with its entire authorization body - the Gate::allows('update', $resource) check and the surrounding resource-resolution logic - commented out, turning it into a no-op pass-through. Any multi-user or multi-team Coolify deployment on 4.1.2 or earlier is exposed across application, database, service, server, environment and project update routes; the vendor's CVSS 4.0 vector rates the flaw PR:N while the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L) indicates a valid authenticated Coolify account is realistically required, since the affected routes sit behind login. Publicly available exploit code exists and upgrading to 4.2.0 fixes the issue; there is no CISA KEV listing, so this is not confirmed active exploitation.
OS command injection in Coolify's database service configuration API allows authenticated administrators to execute arbitrary shell commands within Docker container contexts by embedding shell metacharacters into database credential fields. All Coolify versions prior to 4.0.0-beta.474 are affected, covering deployments managing Redis, KeyDB, Dragonfly, ClickHouse, PostgreSQL, and MySQL services. No public exploit code has been identified at time of analysis, and the CVSS PR:H requirement confines the attack surface to already-privileged admin accounts, positioning this as a post-compromise escalation risk rather than an initial access vector.
Server-Side Request Forgery (SSRF) in Coolify's GitHub App integration exposes internal network services and cloud metadata endpoints to authenticated low-privilege users. Versions prior to 4.0.0-beta.471 allow any authenticated user to set the GithubApp api_url field to an arbitrary URL - including RFC 1918 private addresses or cloud instance metadata endpoints like 169.254.169.254 - which Coolify then fetches server-side without restriction. No public exploit identified at time of analysis, but the attack pattern is well understood and particularly dangerous in cloud-hosted deployments where metadata endpoints may expose IAM credentials.
Server-Side Request Forgery (SSRF) in Coolify prior to v4.0.0-beta.474 enables an authenticated user holding storage management permissions to coerce the application server into issuing HTTP requests to arbitrary internal addresses, including cloud instance metadata services. The vulnerable code path is Coolify's S3 storage endpoint testConnection() function, which blindly fetches the caller-supplied URL after only superficial format validation. No public exploit or CISA KEV listing exists at time of analysis, but cloud-hosted deployments face elevated risk because successful exploitation can expose cloud provider credentials via metadata endpoints such as AWS IMDSv1.
Command injection in Coolify's DatabaseBackupJob allows authenticated users holding database management permissions to execute arbitrary OS commands on managed servers by embedding shell metacharacters in database credentials or MongoDB collection exclusion names. All Coolify releases prior to 4.0.0-beta.471 are affected. No public exploit code has been identified at time of analysis and the vulnerability is absent from CISA KEV; however, the practical impact substantially exceeds the official CVSS 3.3 Low rating because successful exploitation grants attacker-controlled shell execution on production infrastructure managed by the platform.
Coolify's database backup restore file upload endpoint accepts uploads without enforcing any file type or size constraints, enabling an authenticated user to degrade service availability by uploading oversized or unexpected files. All releases prior to 4.0.0-beta.474 are affected per CPE cpe:2.3:a:coollabsio:coolify. No public exploit code exists and the vulnerability is not listed in CISA KEV; with a CVSS score of 3.1 and availability-only impact, this represents a low-priority issue for most operators, especially given the authenticated access requirement.
Password reset poisoning in Coolify prior to 4.0.0-beta.471 enables unauthenticated account takeover by injecting a forged X-Forwarded-Host header during a password reset request. Two compounding middleware failures make this possible: TrustProxies trusts all proxy sources unconditionally, and TrustHosts is rendered inoperable by a circular caching dependency, meaning the Host header is never validated. The reset URL is generated from the spoofed request host, so the victim's reset token is delivered to an attacker-controlled domain. No public exploit is identified at time of analysis, but the attack is low-friction and the fix is confirmed in version 4.0.0-beta.471.
Sanctum API tokens in Coolify never expire prior to v4.0.0-beta.474, meaning any token that is leaked or stolen remains permanently valid until an administrator manually revokes it. This affects the self-hosted server, application, and database management platform across all versions below 4.0.0-beta.474. An attacker who obtains a valid API token via secondary means retains indefinite read access to the Coolify API without natural time-bounded expiry as a safeguard. No public exploit has been identified at time of analysis, and the low CVSS score of 3.1 reflects the constrained real-world impact.
Insecure Direct Object Reference (IDOR) in Coolify's ActivityMonitor Livewire component allows any authenticated user to enumerate and read activity records belonging to other teams, including full SSH process command outputs that may contain secrets, credentials, and infrastructure configuration details. Affected are all Coolify self-hosted deployments prior to version 4.0.0-beta.471. No special privileges beyond a valid user account are required, and auto-incrementing integer activity IDs make enumeration trivial. No public exploit code has been identified at time of analysis and this CVE is not in CISA KEV, but the low attack complexity and sensitive data exposure make this a meaningful risk for multi-tenant Coolify deployments.
Command injection in Coolify's MongoDB backup handler (versions 4.0.0-beta.451 through 4.0.0-beta.470) allows a highly privileged attacker who controls backup configuration to inject OS-level shell commands via unsanitized metacharacters in MongoDB collection names. The attack requires an already-administrative account capable of modifying backup inputs, substantially limiting the realistic threat surface. No public exploit has been identified and this vulnerability is not listed in CISA KEV; the vendor released a fix in v4.0.0-beta.471.
OS command injection in Coolify's settings module allows a highly privileged attacker in a development environment to execute arbitrary shell commands on the host server by injecting metacharacters into the dev_helper_version field, which is passed unsanitized into a Docker build command. All Coolify releases prior to 4.0.0-beta.474 are affected. No public exploit code exists and no CISA KEV listing has been issued; the provided CVSS score of 3.8 (Low) accurately reflects the highly constrained exploitation prerequisites, though the underlying command injection class warrants upgrade regardless.
Unauthenticated access to Coolify's POST /api/feedback endpoint allows any remote attacker to forward arbitrary content directly to the operator's configured Discord webhook, enabling spam flooding, content injection, and webhook rate-limit abuse. All self-hosted Coolify instances prior to 4.0.0-beta.474 are affected, with CVSS AV:N/AC:L/PR:N/UI:N confirming zero-barrier network exploitation. No public exploit code has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, but the trivial exploit conditions (plain unauthenticated HTTP POST) make automated abuse straightforward.
Missing authorization in Coolify's Settings/Updates Livewire component allows any authenticated non-admin user to access the Updates settings page and modify auto-update behavior or trigger update checks. Affected versions span all releases prior to 4.0.0-beta.471 of the self-hosted server management platform. No public exploit code or CISA KEV listing exists at time of analysis, but the network-accessible nature and low authentication bar (any valid account) make this a meaningful integrity risk in multi-tenant or shared Coolify deployments.
Incorrect authorization in Coolify's API layer allows any holder of a read-scoped API token to invoke mutating validation endpoints - including cloud token validation and server validation - that should require write-level privileges. All Coolify deployments prior to version 4.0.0-beta.466 are affected. No public exploit or active exploitation has been identified at time of analysis, but the low attack complexity and network accessibility via API make this straightforward to abuse for any user who has been issued even a minimal API token.
Information disclosure in Coolify allows any authenticated API user to enumerate domain names (FQDNs) of applications belonging to other teams. The issue exists in versions before 4.0.0-beta.464 and is fixed in that release. No active exploitation or public exploit code has been identified, and EPSS predicts very low exploitation probability.
Command injection in Coolify prior to 4.0.0-beta.464 allows authenticated administrators to escape the Docker container and execute arbitrary commands on the host server. The vulnerability originates from the executeInDocker() helper that wraps commands in bash -c '{$command}' without escaping single quotes, enabling injection via user-controlled Docker compose fields. A proof-of-concept exploit exists, but no active exploitation is reported (EPSS 0.22%, low risk).
Authenticated users can access deployment details of any team in Coolify prior to version 4.0.0-beta.464, bypassing team-based authorization. The vulnerability exposes sensitive deployment configuration and metadata, requiring only low-privilege authentication and no user interaction. A public proof-of-concept exists, but EPSS indicates a low probability of widespread exploitation (0.21%).
Information disclosure in Coolify API allows authenticated users to retrieve deployment records from arbitrary teams prior to version 4.0.0-beta.464. By supplying a valid deployment UUID to the /api/v1/deployments/{uuid} endpoint, any low-privileged authenticated user can read deployment details belonging to other teams, violating team isolation. This vulnerability has a CVSS score of 5.0, public exploit code exists, and no active exploitation has been confirmed (CISA KEV absent), with a low EPSS probability of 0.16%.
Coolify's GitLab webhook endpoint leaks its secret token through a timing side-channel, enabling unauthenticated network attackers to reconstruct the token incrementally by measuring HTTP response time differences. All self-hosted Coolify instances prior to 4.0.0-beta.461 with GitLab webhook integrations configured are affected. Once the secret is recovered, an attacker can forge arbitrary GitLab webhook events and potentially trigger unauthorized deployments. No public exploit or active exploitation has been identified at time of analysis; the CVSS-assigned AC:H correctly reflects the practical difficulty of conducting reliable timing measurements over real-world networks.
OS command injection in Coolify 4.0.0's Image Name Handler allows authenticated remote attackers to execute arbitrary operating system commands by manipulating image name inputs. Coolify is a self-hosted PaaS that orchestrates Docker deployments, making server-side command injection in its image handling pipeline particularly high-impact - the platform typically operates with Docker daemon privileges. Publicly available exploit code exists (CVSS 4.0 E:P, corroborated by a GitHub PoC writeup); no public confirmation of active exploitation is present, and no vendor response to the coordinated disclosure was received.
Account takeover in Coolify v4.0.0-beta.434 and earlier is possible because the self-hosted platform's password-reset flow builds the reset link from the attacker-controllable HTTP Host header, so a remote unauthenticated attacker can trigger a reset for a known victim email and have the resulting email point at a server they control - capturing the reset token when the victim clicks the link and using it to set a new password. No authentication is required (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N), but exploitation is per-victim and strictly dependent on the target clicking the poisoned link; instances that pin a canonical application URL or enforce a trusted Host header at a reverse proxy are not exploitable. Publicly available exploit code exists, but there is no confirmed active exploitation in the wild (EPSS is only 0.05%, ~15th percentile) and no vendor-released patch is confirmed as of publication.
Command injection in Coolify up to and including v4.0.0-beta.434 lets any authenticated low-privileged 'member' execute arbitrary system commands as root on the Coolify instance by supplying shell metacharacters in a resource's git source input field. Remote exploitation requires no admin rights and no user interaction, so any team-shared or multi-tenant deployment that lets members create or edit resources is exposed, and this is a genuine high-priority issue rather than a CVSS-inflated one. Publicly available exploit code exists (NVD exploit references including a GitHub security advisory and an accompanying demonstration file), while the EPSS score remains low at 0.47% (64th percentile) and no fixed version was confirmed at the time of publication.
Privilege escalation in Coolify (self-hostable server/application/database management platform) up to and including v4.0.0-beta.434 allows a low-privileged 'member' account to view and redeem administrator invitation links, letting the attacker log in with administrator privileges before the legitimate recipient accepts the invite. Exploitation is not unauthenticated - the CVSS 4.0 vector (PR:L) and our independent CVSS 3.1 assessment (AV:N/AC:H/PR:L/UI:N) confirm the attacker must already hold a valid member account on a shared, multi-user instance, and must win a timing window (AT:P) in which an admin invitation is outstanding and still unclaimed. Publicly available exploit code exists, though there is no confirmed active exploitation (not in CISA KEV) and EPSS is low at 0.05% (16th percentile); real-world risk is therefore moderate and bounded by the member foothold and race-condition prerequisites.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. In Coolify vstarting with version 4.0.0-beta.434, the /login endpoint advertises a rate limit of 5 requests but can be trivially bypassed by rotating the X-Forwarded-For header. [CVSS 4.3 MEDIUM]
Privilege escalation in Coolify (coollabs) up to and including v4.0.0-beta.434 lets an authenticated low-privileged member gain full administrator control by abusing the team invitation workflow: the first attempt to invite an administrator-level user returns an error, but re-submitting the same invite succeeds and creates the higher-privileged account. The attacker can then initiate a password reset against that newly created admin identity and log in as an administrator, achieving complete compromise of the instance (high confidentiality, integrity, and availability impact). Exploitation requires a valid low-privileged member account and no victim interaction; publicly available exploit code exists (GitHub advisory GHSA-4p6r-m39m-9cm9), there is no confirmation of active exploitation, and EPSS is low at roughly 0.04% (13th percentile).
Coolify instances running v4.0.0-beta.434 or earlier expose the root user's private SSH key to any authenticated low-privilege user, turning a limited application account into full root access on the underlying host (C:H/I:H/A:H, CVSS 8.8). The vulnerable path requires an existing low-privilege Coolify account (PR:L per the vector) and then yields the root SSH key with no further interaction, though escalating to root also requires network reachability of the host's SSH service. Publicly available exploit code exists and the EPSS score is low (0.05%, 16th percentile), and as of publication it is unclear whether a vendor patch is available, so multi-user or multi-tenant Coolify deployments are the primary risk population while single-operator installations with no additional low-privilege users have effectively no exposed attacker population.
Command injection in Coolify instances running versions prior to 4.0.0-beta.445 lets an attacker who controls the Git repository used to create an application execute arbitrary commands as root on the Coolify host. The flaw is triggered when a victim user creates or deploys an application using the 'docker compose' build pack from an attacker-supplied repository whose docker-compose.yaml supplies unsanitized parameters that are later interpolated into shell commands executed by Coolify. Publicly available exploit code exists, and the CVSS vector (AV:N/AC:L/PR:N/UI:R) confirms a remote, unauthenticated attack path that nevertheless requires the victim to initiate the build, so real-world exploitation is gated by social engineering rather than direct remote access; EPSS is low at roughly 0.09% (26th percentile). A vendor patch is available in version 4.0.0-beta.445.
Coolify versions up to 4.0.0 contains a vulnerability that allows attackers to a malicious actor to perform an unauthorized email address change on behalf of t (CVSS 5.7).
Stored cross-site scripting in Coolify versions up to and including v4.0.0-beta.420.6 lets an authenticated low-privilege member create a project whose name contains JavaScript; the payload runs in an administrator's browser when the admin later opens the delete flow for that project or an associated resource. Publicly available exploit code exists, but EPSS is low (0.05%, 15th percentile) and no CISA KEV active-exploitation signal was provided, so practical priority is moderate despite the vendor's CVSS 4.0 base of 9.4; the independent CVSS 3.1 assessment is AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, reflecting the need for a member account and administrator interaction. Exposure mainly affects multi-tenant or team deployments where untrusted members can create projects, while single-admin self-hosted instances without untrusted members are effectively not exposed.
Command injection in Coolify's Git Repository field during project creation allows an authenticated member account to run arbitrary shell commands on the self-hosted Coolify server when the project's deployment workflow executes. All releases prior to 4.0.0-beta.420.7 are affected, and publicly available exploit code exists, so member-restricted instances that permit untrusted or self-registered users carry real risk. Exploitation is access-gated rather than anonymous: the CVSS vector (PR:L, AV:N, UI:N) confirms a low-privileged authenticated attacker is required, and the EPSS score of 0.26% (49th percentile) indicates low observed exploitation activity with no CISA KEV listing at time of analysis.
Remote code execution on the host OS is possible through Coolify's application deployment workflow prior to version 4.0.0-beta.420.7, where an authenticated member-level user can inject malicious Docker Compose directives-such as bind mounts of the host filesystem-during project creation or updates. This bypasses container isolation and yields root-level command execution on the Coolify host. Publicly available exploit code exists, and while the EPSS score is modest at 0.42% (62nd percentile), the severity is high because exploitation requires only a low-privileged team account and no user interaction; a vendor patch is available.
Authenticated Coolify users who hold application or service management permissions can execute arbitrary commands as root on managed servers by supplying a crafted file_storage_directory_source value in the File Storage Directory Mount Path feature. The parameter reaches shell command construction without sanitization, so shell metacharacters enable full host compromise; no victim interaction is required, but the attacker must already be authenticated with management rights. Publicly available exploit code exists, the vendor fixed the flaw in 4.0.0-beta.451, and EPSS is low at 0.20%, suggesting limited observed exploitation at time of analysis.
Authenticated command injection in Coolify before 4.0.0-beta.451 lets users with application or service management permissions execute arbitrary commands as root on managed servers by supplying a Dynamic Proxy Configuration filename containing shell metacharacters. Exploitation requires a valid low-privilege Coolify account and no user interaction; unauthenticated or read-only users cannot trigger it directly. Publicly available exploit code exists, but EPSS is only 0.20% (41st percentile), and risk is concentrated in multi-user or shared deployments where service-management roles are broadly granted or an operator account is compromised.
Authenticated command injection in Coolify's PostgreSQL initialization-script filename handling allows users with application or service management permissions to execute arbitrary commands as root on managed servers. All Coolify 4.0.0 beta builds prior to beta.451 are affected, publicly available exploit code exists, and the upstream fix also covers database names used in backup configuration. EPSS is low at 0.41% (61st percentile), but the impact is severe for multi-user or multi-tenant deployments where lower-trust operators hold management rights.
Coolify versions prior to 4.0.0-beta.451 pass user-supplied database names unsanitized into shell commands executed via docker exec on managed servers, allowing an authenticated user with application/service management permissions to run arbitrary commands as root. Exploitation is remote but requires a valid management-capable account (PR:L), so the realistic exposure is multi-user, multi-tenant, or credential-compromise scenarios rather than anonymous mass exploitation. Publicly available exploit code exists and EPSS is modest at 0.41% (61st percentile); no confirmed active exploitation (CISA KEV) at time of analysis.
Authenticated command injection in Coolify before 4.0.0-beta.451 allows users with application or service management permissions to execute arbitrary commands as root on managed servers through the Database Backup feature. The flaw is caused by database names being inserted into shell commands without sanitization when backup jobs invoke mongodump, pg_dump, mysqldump, and mariadb-dump via docker exec; publicly available exploit code exists and EPSS is 0.20% (42nd percentile). The vendor-released patch is version 4.0.0-beta.451, and no CISA KEV confirmation was provided in the available data.
Coolify versions prior to v4.0.0-beta.420.7 are vulnerable to a remote code execution vulnerability in the project deployment workflow. Rated critical severity (CVSS 9.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Coolify versions prior to v4.0.0-beta.420.6 are vulnerable to a remote code execution vulnerability in the application deployment workflow. Rated critical severity (CVSS 9.4), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Coolify versions prior to v4.0.0-beta.420.6 are vulnerable to a stored cross-site scripting (XSS) attack in the project creation workflow. Rated critical severity (CVSS 9.4), this vulnerability is remotely exploitable, low attack complexity. No vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated low severity (CVSS 1.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated critical severity (CVSS 10.0), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated critical severity (CVSS 9.9), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated medium severity (CVSS 5.7), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated critical severity (CVSS 10.0), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated medium severity (CVSS 4.7), this vulnerability is low attack complexity. No vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated high severity (CVSS 8.5), this vulnerability is low attack complexity. Public exploit code available and no vendor patch available.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Rated high severity (CVSS 8.5), this vulnerability is low attack complexity. Public exploit code available.