Is CVE-2026-34034 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-34034 being exploited in the wild.

How severe is CVE-2026-34034?

High severity, with a CVSS score of 8.8, published 7 July 2026.

Which products and versions are affected?

coollabsio Coolify < 4.0.0-beta.466.

Is there a fix for CVE-2026-34034?

A patch was published on 2026-07-07: CVE published and fix confirmed in version 4.0.0-beta.466 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-34034 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-34034?

Check whether anything you run is named in the advisory. 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.

CVE-2026-34034: Coolify OS command injection in Sentinel token settings

Q: Which products and versions are affected?

coollabsio Coolify < 4.0.0-beta.466.

Q: Is there a fix for CVE-2026-34034?

A patch was published on 2026-07-07: CVE published and fix confirmed in version 4.0.0-beta.466 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-34034 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-34034?

Check whether anything you run is named in the advisory. 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.

CVE-2026-34034 · Severity: high · CVSS 8.8 · Published 2026-07-07

Coolify is an open-source platform used to manage and deploy servers, applications, and databases. A security flaw allows an authorized user to execute malicious commands on the underlying server by entering specially crafted text into the Sentinel monitoring settings. This could lead to a complete takeover of the server, unauthorized access to hosted data, and disruption of all managed services.

Quick answers

Is CVE-2026-34034 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-34034 being exploited in the wild.
How severe is CVE-2026-34034?: High severity, with a CVSS score of 8.8, published 7 July 2026.
Which products and versions are affected?: coollabsio Coolify < 4.0.0-beta.466.
Is there a fix for CVE-2026-34034?: A patch was published on 2026-07-07: CVE published and fix confirmed in version 4.0.0-beta.466 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-34034 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-34034?: Check whether anything you run is named in the advisory. 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 (CWE-78) exists in Coolify's Sentinel monitoring component. The root cause is the improper neutralization of the 'sentinel_token' variable, which is directly interpolated into shell commands within 'app/Actions/Server/StartSentinel.php' and other components during Docker startup and metrics collection. An authenticated attacker with access to server settings can provide a malicious token containing shell metacharacters (e.g., quotes and semicolons). When the Sentinel service is automatically restarted or metrics are requested, the injected commands are executed on the host with the privileges of the Coolify process. This issue is resolved in version 4.0.0-beta.466 by implementing strict token validation.

Affected products

coollabsio Coolify < 4.0.0-beta.466

Timeline

2026-03-04: disclosed: Vulnerability discovered by Xyptonize
2026-07-02: advisory: GitHub Security Advisory published
2026-07-07: patched: CVE published and fix confirmed in version 4.0.0-beta.466

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.