Quick answers
- Is CVE-2026-34168 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34168 being exploited in the wild.
- How severe is CVE-2026-34168?
- High severity, with a CVSS score of 8.8, published 7 July 2026.
- Which products and versions are affected?
- Coollabs Coolify < 4.0.0-beta.471.
- Is there a fix for CVE-2026-34168?
- A patch was published on 2026-03-26: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34168 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-34168?
- Check whether you run Coollabs Coolify at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An OS command injection vulnerability exists in Coolify due to improper neutralization of special elements in the 'LocalPersistentVolume.name' field. The application interpolates this field directly into shell commands (e.g., 'docker volume rm -f $storage->name') without using 'escapeshellarg()' or equivalent sanitization. An authenticated attacker can use the API to create a storage volume with a name containing shell metacharacters (e.g., '$(curl attacker.com)'). When the resource is subsequently deleted, the 'DeleteService' action executes the injected commands on the managed server via 'instant_remote_process'. This issue is fixed in version 4.0.0-beta.471 by implementing proper shell escaping and input validation.
Affected products
- coollabsio Coolify < 4.0.0-beta.471
Timeline
- 2026-03-26: patched: Fix committed to repository
- 2026-07-02: advisory: GitHub Security Advisory published
- 2026-07-07: disclosed: CVE published to NVD