Skip to main content

Coolify EUVDEUVD-2026-41982

| CVE-2026-34035 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 dashboard
  2. Delivery
    Set malicious log drain secret or env value
  3. Exploit
    Shell interpolates payload without encoding
  4. Execution
    Host shell executes injected commands
  5. Impact
    Code execution and pivot to managed hosts

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 the ability to set a log drain secret or an environment variable value - those specific fields are interpolated into host shell commands without sufficient encoding, so supplying shell metacharacters in either is the trigger. Limiting factors: the attacker must already possess valid credentials on the Coolify instance and be able to reach the dashboard over the network; there is no unauthenticated path and no user interaction is required. Exposure is greatest on internet-facing, multi-user instances prior to 4.0.0-beta.466; single-trusted-operator or network-isolated deployments materially limit realistic exploitation.

Impact

The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8 High) indicates network-reachable, low-complexity exploitation requiring only low privileges (an authenticated Coolify user) and no user interaction, with high impact to confidentiality, integrity and availability - consistent with host command execution. No EPSS score, KEV listing, SSVC decision, or POC was provided, so the exploitation-probability and automatable signals are unknown; absence of these signals is not evidence of low risk. The practical priority is high for any internet-exposed Coolify instance with multiple or untrusted users, since the only barrier is a valid low-privilege account and the payoff is host compromise; for single-operator, network-isolated deployments the practical exposure is lower because the attacker must already hold an account.

Exploit ScenarioDerived

An attacker who holds (or registers/phishes) a low-privilege Coolify account configures a log drain or an application environment variable whose value contains shell metacharacters such as a command-substitution payload. When Coolify builds and runs the corresponding shell command on the host, the injected payload executes with the platform's host privileges, giving the attacker code execution and a pivot into managed servers and containers. No public POC is referenced, but the low attack complexity makes weaponization straightforward.

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 (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.

RemediationAI

Vendor-released patch: upgrade to Coolify v4.0.0-beta.466 or later, which corrects the encoding of log drain secret and environment values before they are used in shell commands (see advisory GHSA-3xm2-hqg8-4m2p and release https://github.com/coollabsio/coolify/releases/tag/v4.0.0-beta.466). If you cannot upgrade immediately, restrict who holds Coolify accounts and avoid configuring log drains, and audit or limit the ability of untrusted users to set environment variables or log drain secrets, since those are the injection sinks; also place the Coolify dashboard behind a VPN or IP allowlist rather than exposing it to the internet to shrink the authenticated attack surface. These controls reduce exposure but do not fully close the flaw and may disrupt legitimate log-drain and multi-user workflows, so upgrading remains the only complete fix.

Affected VersionsENISA

coolify < 4.0.0-beta.466

Affected Packages

euvd coolify fix: 4.0.0-beta.466

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 (an alternative to Heroku/Netlify) that manages servers, applications and databases, frequently running with broad privileges over Docker and the host OS. The root cause is CWE-78 (Improper Neutralization of Special Elements used in an OS Command): user-controlled log drain secrets and environment variable values are concatenated into shell command strings without sufficient encoding or quoting, so shell metacharacters (for example ; | $() or backticks) break out of the intended argument and are executed by the host shell. The affected product per CPE is cpe:2.3:a:coollabsio:coolify covering all versions prior to the fixed 4.0.0-beta.466.

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 dashboard, low complexity, needs a low-privilege authenticated account (PR:L), no user interaction; 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.466, log drain secret and environment values were interpolated into shell commands without sufficient encoding, allowing an authenticated user to inject commands executed on the host. This issue is fixed in version 4.0.0-beta.466.

Executive ViewAI

Why It Matters

Coolify before version 4.0.0-beta.466 contains an authenticated command injection vulnerability (CVSS 8.8) in log drain and environment variable handling that permits arbitrary code execution with host-level privileges. Organizations running vulnerable instances face complete infrastructure takeover; an attacker with Coolify administrative credentials can compromise all containerized applications and underlying systems orchestrated by the platform. No vendor patch is currently available, creating urgent need for interim compensating controls.

Business Impact: Severe
Compensating Controls

Until vendor patch releases: (1) Enforce multi-factor authentication on all Coolify administrative accounts and strictly limit access to essential personnel only; (2) Implement network segmentation to restrict Coolify management interfaces to bastion hosts and approved networks only; (3) Disable log drain and environment interpolation features if operationally feasible; (4) Deploy endpoint detection and response (EDR) monitoring configured to alert on unexpected shell command execution spawned by Coolify processes; (5) Enable comprehensive audit logging of all configuration changes within Coolify; (6) If available, implement reverse proxy or WAF rules to validate and encode all inputs to log drain and environment variable fields.

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Medium
popular open-source self-hosted PaaS, but niche versus enterprise platforms
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

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
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
Very 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