# CVE-2026-34034: Coolify: Host RCE via Sentinel token injection

> An authenticated user can inject shell commands via the Sentinel token setting to execute arbitrary code on the host server.

- **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:** 7 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-rpr8-p7jc-x844

## What is CVE-2026-34034?

CVE-2026-34034 is a high-severity command injection vulnerability in coollabsio coolify, published on 7 Jul 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.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.

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

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


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

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

## Is CVE-2026-34034 being exploited?

There is no known exploitation of CVE-2026-34034 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34034 is a high-severity command injection vulnerability in coollabsio coolify, published on 7 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34034 in the wild and no public exploit code.

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-34034/ (Markdown: https://insights.sbomify.com/CVE-2026-34034/index.md)
```

## Sources

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

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