dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-34597

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

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

This is an authenticated command injection vulnerability in Coolify's Nixpacks build pack. The install_command parameter is directly concatenated into a shell command string without sanitization, allowing an authenticated attacker to escape the build context and execute arbitrary commands with host-level privileges during the deployment build phase.

MitigationUpgrade Coolify to version 4.0.0-beta.470 or later. Until then, restrict access to users who can configure build parameters and monitor for suspicious build commands.

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 your Coolify version
    Access the Coolify administration panel or check the running container/image version. Common ways: check the dashboard UI for version info, or run 'coolify --version' or check the docker/container labels if self-hosted.
    Affected if The installed version is any release prior to 4.0.0-beta.470 (e.g., 4.0.0-beta.460, 4.0.0-beta.400, 3.x.x, etc.)
  2. Confirm Nixpacks build pack is in use
    Review your Coolify project or application settings. Navigate to the Build Pack or Build Settings section for your deployed application and identify which build pack is selected. Look for 'Nixpacks' as the active build pack.
    Affected if Nixpacks is selected as the build pack for the application
  3. Examine install_command configuration
    In the application's build configuration settings, locate the 'install_command' or similar parameter field under the Nixpacks settings. Inspect whether any custom value is populated in this field.
    Affected if A custom install_command value is configured (non-empty or non-default) in the Nixpacks build settings
  4. Verify user access to build configuration
    Check the permissions and roles assigned to users who can modify application settings. Determine which authenticated users have the ability to edit build parameters, install commands, or similar build pack settings.
    Affected if Any authenticated user (beyond strictly privileged administrators) has write access to modify build parameters or the install_command field

You are affected if your Coolify version is prior to 4.0.0-beta.470 AND you use the Nixpacks build pack with any user-configurable install_command parameter accessible to authenticated users.

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.470 or later. Until then, restrict access to users who can configure build parameters and monitor for suspicious build commands.

Recommended fix High confidence

4.0.0-beta.470

  1. Upgrade Coolify to version 4.0.0-beta.470 or later to remediate the authenticated RCE vulnerability in the Nixpacks build pack.
Caveat This is a beta version upgrade; review release notes for potential stability or configuration changes.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34597 — 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-34597 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