# CVE-2026-34038: Coolify authenticated remote command injection leading to RCE and secret exfiltration

> Authenticated users with write permissions can inject commands to execute code and steal secrets via deployment logs.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 6 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-qqrq-r9h4-x6wp

## What is CVE-2026-34038?

CVE-2026-34038 is a critical command injection vulnerability in coollabsio coolify, published on 6 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.469, an authenticated remote command injection vulnerability in application deployment handling allows users with application write permissions to achieve remote code execution and exfiltrate sensitive environment variables through deployment logs via fields such as dockerfile_location and deployment commands. This issue is fixed in version 4.0.0-beta.469.

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

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


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

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

## Is CVE-2026-34038 being exploited?

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

Public exploit code:

- CVE-2026-34038: Authenticated Remote Command Injection in Coolify (github_poc): https://github.com/ThemeHackers/CVE-2026-34038

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34038 is a critical command injection vulnerability in coollabsio coolify, published on 6 Jul 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-34038 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-34038/ (Markdown: https://insights.sbomify.com/CVE-2026-34038/index.md)
```

## Sources

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

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