CVE-2026-59734
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 · uneditedCoolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.469, Coolify's app/Jobs/ApplicationDeploymentJob.php generate_healthcheck_commands() function directly interpolated the health_check_host, health_check_method, and health_check_path parameters into shell commands without proper sanitization, allowing authenticated users to execute arbitrary commands inside deployment containers. This issue is fixed in version 4.0.0-beta.469.
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 confidenceCoolify versions prior to 4.0.0-beta.469 contain a command injection vulnerability in the generate_healthcheck_commands() function within ApplicationDeploymentJob.php. Authenticated users can manipulate health_check_host, health_check_method, and health_check_path parameters to inject arbitrary shell commands that execute within deployment containers.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Coolify versionRun 'coolify --version' from the Coolify CLI or check the version displayed in the Coolify web UI dashboardAffected if Version is lower than 4.0.0-beta.469 (e.g., 4.0.0-beta.450, 3.x.x releases)
-
Verify health check configuration accessNavigate to application deployment settings in Coolify UI and review health_check_host, health_check_method, and health_check_path parameters for any custom or user-supplied valuesAffected if Health check parameters are configurable by users and the Coolify version is below 4.0.0-beta.469
-
Inspect deployment container logsExamine logs from recent application deployments for unusual shell command patterns, unexpected payloads, or suspicious strings in health check related entriesAffected if Logs contain commands or arguments that were not explicitly defined by administrators, indicating potential injection attempts
-
Review user permissions on deployment workflowsCheck which user roles have access to modify application health check configuration in the Coolify administration panelAffected if Non-admin or untrusted users have permission to configure health check parameters and the Coolify version is vulnerable
You are affected if your Coolify version is prior to 4.0.0-beta.469 and users with deployment access can configure health check parameters.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Coolify to version 4.0.0-beta.469 or later. Until then, restrict access to health check configuration to trusted personnel only and monitor for suspicious command patterns in container logs.
4.0.0-beta.469
- Upgrade Coolify to version 4.0.0-beta.469 or later to resolve the command injection vulnerability in the generate_healthcheck_commands() function
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59734 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-59734 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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