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

CVE-2026-34034 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-34034?

Coolify deployments before v4.0.0-beta.466 contain an authenticated command injection vulnerability (CVSS 8.8) that grants attackers with server Sentinel access full host command execution,…. A patch is available.

How to fix or mitigate CVE-2026-34034?

Within 24 hours: identify all Coolify deployments and document current versions; within 7 days: deploy v4.0.0-beta.466 or later across all instances (test in staging first to validate compatibility); within 30 days: audit access controls to Sentinel settings and implement principle-of-least-privilege restrictions on server configuration roles.

Coolify CVE-2026-34034

EUVD-2026-41987 HIGH

OS Command Injection (CWE-78)

2026-07-07 GitHub_M

Command Injection Coolify Coollabsio

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

7.2 HIGH

Editing server Sentinel settings is a privileged/admin action so PR:H; network-reachable web UI keeps AV:N/AC:L, and host command execution gives full C:H/I:H/A:H.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:H/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 - 04:10 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.466, the sentinel_token setting is used in shell commands without sufficient validation, allowing an authenticated user with access to server Sentinel settings to inject shell syntax and execute commands on the host when Sentinel is restarted. This issue is fixed in version 4.0.0-beta.466.

AnalysisAI

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.

Technical ContextAI

Coolify is an open-source, self-hostable PaaS (a Heroku/Netlify alternative) that provisions and manages remote servers, applications, and databases. 'Sentinel' is Coolify's lightweight monitoring agent deployed to managed servers; it is configured with a sentinel_token used for authentication between the control plane and the agent. The affected component is identified by CPE cpe:2.3:a:coollabsio:coolify:*:*:*:*:*:*:*:* covering all releases prior to the fix. The root cause is CWE-78 (Improper Neutralization of Special Elements used in an OS Command): the sentinel_token string is interpolated into a shell command line without validation or safe argument passing, so any shell syntax it contains (backticks, ;, $(), &&, pipes) is interpreted by the shell rather than treated as literal data. Execution is deferred until the Sentinel service is (re)started, at which point the command is assembled and run on the host.

RemediationAI

Vendor-released patch: v4.0.0-beta.466 - upgrade Coolify to 4.0.0-beta.466 or later, which fixes the input validation of sentinel_token (upstream fix commit https://github.com/coollabsio/coolify/commit/096d4369e59b3db7ace2db3ca42588c41b9b6019; advisory https://github.com/coollabsio/coolify/security/advisories/GHSA-rpr8-p7jc-x844; release https://github.com/coollabsio/coolify/releases/tag/v4.0.0-beta.466). If you cannot upgrade immediately, restrict who can edit server Sentinel settings to a minimal set of fully trusted administrators (remove elevated roles from any non-trusted team members), and avoid restarting Sentinel on servers whose token may have been tampered with until values are reviewed. As a stopgap, audit the current sentinel_token values for shell metacharacters (backticks, $(), ;, &&, |) before any Sentinel restart, and consider disabling Sentinel monitoring on exposed servers until patched - trade-off: you lose host/agent telemetry while it is disabled. These are compensating controls only; upgrading is the sole complete fix.