What is the CVSS score of CVE-2026-42201?

CVE-2026-42201 has a CVSS 3.1 base score of 3.3 (Low). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N. EPSS exploitation probability: 0.2%.

Is there a patch available for CVE-2026-42201?

Yes, a patch is available for CVE-2026-42201. Update the affected software to the latest version immediately.

Coolify CVE-2026-42201

EUVD-2026-41999 LOW

OS Command Injection (CWE-78)

2026-07-07 GitHub_M

Docker Command Injection Coolify Coollabsio

3.3

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

3.3 LOW

AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N

vuln.today AI

3.3 LOW

Admin credentials required (PR:H) and YAML-plus-shell payload crafting complexity (AC:H) dominate; container-scoped limited reads and writes justify C:L/I:L with no availability impact.

3.1 AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N

4.0 AV:N/AC:H/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

High

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Patch available

Jul 07, 2026 - 06:16 EUVD

Analysis Generated

Jul 07, 2026 - 05:17 vuln.today

DescriptionCVE.org

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.474, database credential fields (redis_password, keydb_password, dragonfly_password, clickhouse_admin_user, clickhouse_admin_password, postgres_user, mysql_user) are validated only as 'string' at the API layer, with zero shell-safety checks. These values are then interpolated directly into Docker Compose YAML command: strings without any escaping. This issue is fixed in version 4.0.0-beta.474.

AnalysisAI

OS command injection in Coolify's database service configuration API allows authenticated administrators to execute arbitrary shell commands within Docker container contexts by embedding shell metacharacters into database credential fields. All Coolify versions prior to 4.0.0-beta.474 are affected, covering deployments managing Redis, KeyDB, Dragonfly, ClickHouse, PostgreSQL, and MySQL services. No public exploit code has been identified at time of analysis, and the CVSS PR:H requirement confines the attack surface to already-privileged admin accounts, positioning this as a post-compromise escalation risk rather than an initial access vector.

Technical ContextAI

Coolify is an open-source self-hosting management platform (CPE: cpe:2.3:a:coollabsio:coolify) that provisions and orchestrates Docker-based applications and databases. The root cause is CWE-78 (Improper Neutralization of Special Elements used in an OS Command). Credential fields - redis_password, keydb_password, dragonfly_password, clickhouse_admin_user, clickhouse_admin_password, postgres_user, and mysql_user - are validated only as generic string types at the API layer without any shell-safety filtering. These raw values are then interpolated verbatim into Docker Compose YAML command: strings, which the Docker daemon executes when containers are created or restarted. Because the YAML command: key passes its value through a shell, embedded metacharacters such as semicolons, backticks, or $() subshells are interpreted as OS-level commands in the container execution context. The fix introduced in commit bff6d853708f3d7c861279586f107739036e67da adds shell-safe escaping or validation to these fields before YAML interpolation.

RemediationAI

Upgrade to Coolify version 4.0.0-beta.474 or later, which resolves the injection vulnerability per the vendor security advisory at https://github.com/coollabsio/coolify/security/advisories/GHSA-f35h-g2c2-q36v and the corresponding code fix in commit bff6d853708f3d7c861279586f107739036e67da (https://github.com/coollabsio/coolify/pull/9676). As a compensating control prior to patching, audit all existing database credential field values in your Coolify instance for embedded shell metacharacters (semicolons, backticks, dollar-sign subshells, pipe characters) and sanitize any anomalous values. Additionally, restrict Coolify API and UI access to the minimum necessary administrator accounts using network-level ACLs or authentication gating - this reduces the attacker pool but does not eliminate the vulnerability itself. Enabling Docker daemon logging and monitoring container startup commands for unexpected shell executions can serve as a detection layer. Note that neither network restriction nor credential auditing constitutes a full fix; patching to beta.474 is the only remediation.