CVE-2026-42201: coollabsio coolify · OS Command Injection
Affects coollabsio coolifySource CVE Database V5
Not known to be exploited · CVSS 3.3 Low : upgrade to 4.0.0-beta.474 when convenient.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.0.0-beta.474
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade coollabsio coolify to 4.0.0-beta.474.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| coollabsiocoolify | Affected
| Fixed in
|
GitHubcoollabsio/coolifypkg:github/coollabsio/coolifyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Coolify version 4.0.0-beta.474 or later, where this vulnerability is fixed. No other official remediation or temporary fixes are documented. Patch status is not explicitly confirmed beyond the fix in 4.0.0-beta.474, so users should verify vendor advisories for updates.
Description
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.
References
- github.com/coollabsio/coolify/security/advisories/GHSA-f35h-g2c2-q36v (opens in a new tab)
- github.com/coollabsio/coolify/pull/9676 (opens in a new tab)
- github.com/coollabsio/coolify/commit/bff6d853708f3d7c861279586f107739036e67da (opens in a new tab)
- github.com/coollabsio/coolify/releases/tag/v4.0.0-beta.474 (opens in a new tab)