What is the CVSS score of CVE-2026-34597?

CVE-2026-34597 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.5%.

Which versions of Coolify are affected by CVE-2026-34597?

Coolify versions before 4.0.0-beta.470 contain an authenticated remote code execution vulnerability in the Nixpacks build pack that allows low-privileged users to execute arbitrary commands on the…. A patch is available.

Is there a public PoC exploit available for CVE-2026-34597?

Yes, a public proof-of-concept exploit is available for CVE-2026-34597. Prioritise patching immediately. EPSS: 0.5%.

How to fix or mitigate CVE-2026-34597?

Within 24 hours: Audit all Coolify instances to confirm versions and restrict build configuration permissions to administrators only; disable Nixpacks builds if not actively required. Within 7 days: Subscribe to Coolify security updates and prepare to apply 4.0.0-beta.470 or later immediately upon release; implement network segmentation to limit lateral movement from the deployment host. Within 30 days: Complete migration to patched version or evaluate alternative PaaS solutions if vendor patch timeline extends beyond critical risk tolerance.

Coolify CVE-2026-34597

EUVD-2026-40224 HIGH

OS Command Injection (CWE-78)

2026-06-29 GitHub_M

Command Injection RCE Coolify

8.8

CVSS 3.1 · Vendor: GitHub_M

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) with simple injection (AC:L) by an authenticated config-capable user (PR:L) yields host RCE with 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

Patch available

Jun 29, 2026 - 22:02 EUVD

Analysis Generated

Jun 29, 2026 - 21:15 vuln.today

DescriptionCVE.org

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.470, a critical Authenticated Host Remote Code Execution (RCE) vulnerability was discovered in Coolify. The flaw resides in the handling of user-defined build parameters for the Nixpacks build pack. Specifically, the install_command provided by a user is directly concatenated into a shell command string that is executed on the deployment host during the building phase. An attacker can leverage this to escape the intended build context and execute arbitrary commands with host-level privileges. This vulnerability is fixed in 4.0.0-beta.470.

AnalysisAI

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.

Technical ContextAI

Coolify is an open-source, self-hostable alternative to Heroku/Netlify for deploying applications, databases, and managing servers. It supports multiple build packs, including Nixpacks, which generates build environments automatically. The root cause is CWE-78 (Improper Neutralization of Special Elements used in an OS Command, i.e. OS command injection): the install_command field that users define for the Nixpacks build is injected directly into a shell command string that Coolify executes on the deployment host. Because shell metacharacters are not neutralized, supplied input is interpreted by the shell rather than treated as inert data. The affected component per CPE is cpe:2.3:a:coollabsio:coolify, all versions prior to the fixed 4.0.0-beta.470.

RemediationAI

Upgrade to the patched release Coolify 4.0.0-beta.470, which contains the fix (Vendor-released patch: 4.0.0-beta.470); see the advisory at https://github.com/coollabsio/coolify/security/advisories/GHSA-9pp4-wcmj-rq73. Until upgrading, restrict who can create or modify deployments and build configurations so that only fully trusted operators hold accounts (this reduces the multi-tenant attack surface but does not eliminate risk from any account that can edit build settings), avoid using the Nixpacks build pack or user-defined install_command values for untrusted projects (trade-off: limits build flexibility), and place the Coolify control panel behind network restrictions or a VPN so the authenticated UI is not broadly reachable (trade-off: less convenient remote access). These are compensating controls only; patching is the sole complete remedy.