dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-34594

HIGH · 8.8 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.471, an authenticated command injection vulnerability in the Destination Network Management functionality allows users with destination management permissions to execute arbitrary commands as root on managed servers. The "network" parameter is passed directly to shell commands without proper sanitization, enabling full remote code execution on the host system. This vulnerability is fixed in 4.0.0-beta.471.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An authenticated command injection vulnerability exists in Coolify's Destination Network Management functionality. The 'network' parameter is passed directly to shell commands without sanitization, allowing authenticated users with destination management permissions to execute arbitrary commands as root on managed servers, achieving full remote code execution.

MitigationUpgrade Coolify to version 4.0.0-beta.471 or later to remediate this vulnerability. Until upgrade is possible, restrict destination management permissions to trusted users only and monitor for suspicious command execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Coolify installation
    Locate the Coolify installation and note its deployment method (Docker container, binary, or other). Check running processes or services for 'coolify' references.
    Affected if Coolify is not installed or not in use.
  2. Determine Coolify version
    Access the Coolify web interface and navigate to the settings or about page to view the installed version number. Alternatively, check the Docker image tag or application metadata if deployed via container.
    Affected if The installed version is lower than 4.0.0-beta.471.
  3. Verify destination management access
    Log into Coolify with the account in question and navigate to the Destination or Server Management section. Confirm whether the user has access to create or modify network configurations for destinations.
    Affected if The authenticated user has destination management permissions enabled.
  4. Inspect network parameter handling
    If you have access to Coolify's backend logs or configuration, examine how the 'network' parameter is processed when configuring a destination. Look for direct shell command construction using this parameter.
    Affected if The network parameter is passed directly to shell commands without visible sanitization in logs or configuration.

You are affected if Coolify is installed with a version lower than 4.0.0-beta.471 and an authenticated user with destination management permissions can access the network configuration feature.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Coolify to version 4.0.0-beta.471 or later to remediate this vulnerability. Until upgrade is possible, restrict destination management permissions to trusted users only and monitor for suspicious command execution.

Recommended fix High confidence

4.0.0-beta.471 or later

  1. Upgrade Coolify to version 4.0.0-beta.471 or later to resolve the command injection vulnerability
  2. Verify the upgrade was successful by checking the Coolify version
  3. Confirm that Destination Network Management functionality works correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34594 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34594 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data