# CVE-2026-34597: Coolify: Authenticated Host RCE

> Authenticated attackers can execute arbitrary commands on the host via Nixpacks build parameters, requiring an upgrade to Coolify.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-9pp4-wcmj-rq73

## What is CVE-2026-34597?

CVE-2026-34597 is a high-severity command injection vulnerability in coollabsio coolify, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-34597?


## How do I fix CVE-2026-34597?

No fix has been published for CVE-2026-34597 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-34597 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34597 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34597 and fix it if it is affected.

What it is: CVE-2026-34597 is a high-severity command injection vulnerability in coollabsio coolify, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34597 exists.

Affected product: coollabsio coolify. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34597/ (Markdown: https://insights.sbomify.com/CVE-2026-34597/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34597
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34597
- OSV: https://osv.dev/vulnerability/CVE-2026-34597

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34597/
Summaries are generated and may contain mistakes; the official description above is the record.