Skip to main content

Coolify EUVDEUVD-2026-41994

| CVE-2026-34057 HIGH
OS Command Injection (CWE-78)
2026-07-07 GitHub_M
8.8
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to Coolify with low-priv account
  2. Delivery
    Start a database import
  3. Exploit
    Set container name to shell payload
  4. Execution
    Component builds import shell command
  5. Persist
    Injected command executes on host
  6. Impact
    Full server compromise

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

Requires an authenticated Coolify account (PR:L) with access to the database import feature; the attacker triggers the flaw by supplying a malicious container name (client-controlled container/server properties) to the database import Livewire component in app/Livewire/Project/Database/Import.php. Exploitation is limited by the need for valid credentials and access to a project where a database import can be performed, and by the affected version being prior to 4.0.0-beta.471 - patched instances are not vulnerable. No user interaction from a victim and no elevated/admin privileges are needed, and the vulnerable UI must be network-reachable to the attacker.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U, C:H/I:H/A:H = 8.8) is internally consistent with the description: network-reachable web UI, low complexity, and only a low-privileged authenticated account required for full host compromise. The main limiting factor is PR:L - the attacker must already have a valid Coolify account with access to create/import a database, so this is not an unauthenticated internet-wide worm target; risk concentrates in multi-tenant or team deployments where lower-trust users hold accounts. No EPSS score, KEV entry, or public POC was provided, so real-world exploitation pressure appears low-to-moderate today, but the trivial exploitation mechanics (inject shell metacharacters into a name field) mean weaponization would be straightforward once details are public via the GHSA advisory and the fix commit. No signals conflict here; the primary uncertainty is exploitation prevalence, not exploitability.

Exploit ScenarioDerived

An attacker with a low-privileged but valid Coolify account initiates a database import and sets the container name to a value containing shell metacharacters (e.g. a command-substitution or chained command payload). When Coolify builds and runs the import shell command, the injected payload executes with the privileges of the Coolify worker on the host, granting arbitrary command execution and potential full server takeover. No public POC is currently identified, but the attack requires no special tooling beyond the standard import UI.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 07, 2026

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.

RemediationAI

Vendor-released patch: 4.0.0-beta.471 - upgrade Coolify to 4.0.0-beta.471 or later, which adds server-side locking/validation of the container and server properties before they reach shell commands (fix commit d486bf09ab2da8ad78fa721a079f066c76ce08d2). Until you can upgrade, restrict who holds Coolify accounts and tighten team membership so only fully trusted operators can create or import databases, since the exploit requires an authenticated session; where feasible, avoid exposing the Coolify management UI directly to untrusted networks (place it behind a VPN or IP allowlist) and audit database-import container names for shell metacharacters. These access-restriction workarounds reduce exposure but do not remove the injection, and limiting account provisioning may impede legitimate multi-user workflows, so patching remains the only complete remediation. See the advisory at https://github.com/coollabsio/coolify/security/advisories/GHSA-6r3g-w7x8-54fj.

Affected VersionsENISA

coolify < 4.0.0-beta.471

Affected Packages

euvd coolify fix: 4.0.0-beta.471

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-hostable PaaS (a Heroku/Netlify alternative) that provisions and manages servers, applications, and databases, largely by orchestrating Docker containers through shell commands issued from a PHP/Laravel Livewire backend. The flaw is a classic CWE-78 (OS Command Injection): the database import handler in app/Livewire/Project/Database/Import.php interpolates client-supplied container and server properties (notably the container name) directly into a shell command string. Because these Livewire-bound properties are attacker-controllable and are used without locking (server-side re-validation) or input sanitization, shell metacharacters embedded in the container name break out of the intended command and execute on the host running the Coolify worker.

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

Vendor (GitHub_M) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable web UI (AV:N), simple metacharacter injection (AC:L), requires a valid low-privileged account (PR:L), no victim interaction (UI:N); host command execution yields full C/I/A impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

1
Patch available
Jul 07, 2026 - 05:01 EUVD

DescriptionCVE.org

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.471, the database import Livewire component (app/Livewire/Project/Database/Import.php) allows client-controlled container and server properties to reach shell commands without locking or validation, allowing an authenticated user to inject commands through a database import container name. This issue is fixed in version 4.0.0-beta.471.

Executive ViewAI

Why It Matters

Coolify's self-hosted infrastructure platform contains a vulnerability allowing any authenticated user to execute arbitrary code and gain complete control of underlying servers. This impacts all organizations running Coolify and requires immediate action to restrict user access before credentials are compromised or leveraged for lateral movement.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim controls: restrict Coolify administrative access to infrastructure teams only; disable non-essential database import functionality; implement comprehensive host monitoring and logging; isolate Coolify systems from critical production networks until stable patch is available.

Threat Intelligence Overview

EPSS Score
0.3%
Top 73% exploitable
Prevalence
Low
niche self-hosted PaaS, mostly hobbyist and small-team deployments
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

OS command injection occurs when an application passes unsanitized user input directly into system shell commands.

CVE-2026-57498 CRITICAL POC
9.6 Jun 29

Cross-team authorization bypass in Coolify (open-source self-hosted PaaS) before 4.0.0-beta.474 allows an authenticated,

CVE-2025-34161 CRITICAL POC
9.4 Aug 27

Coolify versions prior to v4.0.0-beta.420.7 are vulnerable to a remote code execution vulnerability in the project deplo

CVE-2025-34159 CRITICAL POC
9.4 Aug 27

Coolify versions prior to v4.0.0-beta.420.6 are vulnerable to a remote code execution vulnerability in the application d

CVE-2025-64424 CRITICAL POC
9.4 Jan 05

Command injection in Coolify up to and including v4.0.0-beta.434 lets any authenticated low-privileged 'member' execute

CVE-2025-59156 CRITICAL POC
9.4 Jan 05

Remote code execution on the host OS is possible through Coolify's application deployment workflow prior to version 4.0.

CVE-2025-66211 CRITICAL POC
9.4 Dec 23

Authenticated command injection in Coolify's PostgreSQL initialization-script filename handling allows users with applic

CVE-2025-66210 CRITICAL POC
9.4 Dec 23

Coolify versions prior to 4.0.0-beta.451 pass user-supplied database names unsanitized into shell commands executed via

CVE-2025-66213 CRITICAL POC
9.4 Dec 23

Authenticated Coolify users who hold application or service management permissions can execute arbitrary commands as roo

CVE-2025-66212 CRITICAL POC
9.4 Dec 23

Authenticated command injection in Coolify before 4.0.0-beta.451 lets users with application or service management permi

CVE-2025-59158 CRITICAL POC
9.4 Jan 05

Stored cross-site scripting in Coolify versions up to and including v4.0.0-beta.420.6 lets an authenticated low-privileg

CVE-2026-34594 HIGH POC
8.8 Jun 29

Authenticated OS command injection in Coolify before 4.0.0-beta.471 lets any user holding destination management permiss

CVE-2026-34597 HIGH POC
8.8 Jun 29

Authenticated remote code execution in Coolify (self-hosted PaaS) before 4.0.0-beta.470 lets a low-privileged authentica

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy