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

CVE-2026-34168 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.4%.

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

Coolify (self-hosted infrastructure management platform) versions before 4.0.0-beta.471 contain an authenticated command injection vulnerability allowing malicious administrators or compromised…. A patch is available.

How to fix or mitigate CVE-2026-34168?

Within 24 hours: Audit all Coolify deployments, document current versions and number of managed servers. Within 7 days: Upgrade all instances to Coolify 4.0.0-beta.471 or later; enforce strong credential policies on Coolify administrator accounts and API tokens. Within 30 days: Review Coolify audit logs for suspicious LocalPersistentVolume deletions; verify integrity of all managed servers for unauthorized changes.

Coolify CVE-2026-34168

EUVD-2026-41986 HIGH

OS Command Injection (CWE-78)

2026-07-07 GitHub_M

Command Injection Docker 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-facing web app where any authenticated user can set volume names gives AV:N/AC:L/PR:L/UI:N; command execution on managed servers yields full C:H/I:H/A:H.

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

Jul 07, 2026 - 05:01 EUVD

Analysis Generated

Jul 07, 2026 - 03:56 vuln.today

CVE Published

Jul 07, 2026 - 03:05 cve.org

HIGH 8.8

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 LocalPersistentVolume.name field is interpolated directly into docker volume shell commands without shell argument escaping, allowing an authenticated user to set a storage name containing shell metacharacters and execute commands on managed servers when the resource is deleted. This issue is fixed in version 4.0.0-beta.471.

AnalysisAI

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.

Technical ContextAI

Coolify is an open-source, self-hostable PaaS/Heroku alternative that orchestrates Docker on one or more managed servers (typically over SSH). The flaw sits in how a persistent storage volume's name (LocalPersistentVolume.name) is passed into a shell command that manages Docker volumes: the value is string-interpolated directly into the command line without shell-argument escaping or quoting. This is a classic CWE-78 OS Command Injection, where attacker-controlled data crosses into a shell interpreter's control plane; the affected component per CPE is cpe:2.3:a:coollabsio:coolify (all versions prior to the fix). Because Coolify runs these docker commands against the servers it manages, the injected payload executes in that server context, not merely inside the Coolify UI container.

RemediationAI

Vendor-released patch: 4.0.0-beta.471 - upgrade the Coolify instance to v4.0.0-beta.471 or later, which is fixed per commit d2064dd4998694cda2eabd00149f7c4d1e94c699 and the release at https://github.com/coollabsio/coolify/releases/tag/v4.0.0-beta.471. Review the advisory at https://github.com/coollabsio/coolify/security/advisories/GHSA-mh8x-fppq-cp77 for details. Until patched, restrict who holds accounts and volume-management permissions on the instance (limit to fully trusted operators), avoid creating or deleting resources whose LocalPersistentVolume names were set by untrusted users, and audit existing storage names for shell metacharacters (semicolon, pipe, dollar-sign, backtick, ampersand) before deleting those resources, since deletion is the trigger. These are interim controls only and reduce usability by tightening account access; upgrading is the reliable fix.