How broadly exploitable is this vulnerability?

Exploitability depends on who controls the repositories used by Coolify. If users routinely deploy applications from third-party or untrusted repositories using the "docker compose" build pack, attackers can potentially exploit this flaw remotely by crafting malicious docker-compose.yaml files.

What level of access does an attacker need to exploit this issue?

An attacker needs the ability to provide or influence the repository from which a victim user creates an application in Coolify. They do not need shell access to the server; the exploitation occurs when Coolify processes the attacker-controlled docker-compose.yaml.

What is the safest general fix pattern for developers?

The most robust fix is to eliminate shell string construction from untrusted data entirely, using safe process execution APIs with explicit argument lists and strict validation/allowlisting of configuration values before they are passed to any command.

Severity:

CRITICAL RISK

(9.6)

Command Injection (CWE-77) via docker-compose Parameters in Coolify

CVE-2025-64419

Published:

Jan 5, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

Remote Code Execution on the Router

April 6, 2026

CWE-77;CWE-78

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Remote Code Execution on Router Firmware

April 6, 2026

Vulnerability Type

Category:

Command Injection

CWE:

CWE-77

Impact:

Remote Code Execution as root on the Coolify host

Severity:

CRITICAL RISK

(9.6)

CVSS Version:

3.1

Vulnerability Type

Category:

Command Injection

CWE:

CWE-77

Impact:

Remote Code Execution as root on the Coolify host

Severity:

CRITICAL RISK

(9.6)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Command Injection (CWE-77) via docker-compose Parameters in Coolify

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setGameSpeedCfg CGI Handler

HIGH RISK

HIGH

(7.3)

OS Command Injection (CWE-78) in Totolink A7100RU setFirewallType Handler

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare