CVE-2026-27881: coollabsio coolify · Insecure Direct Object Reference
Affects coollabsio coolifySource CVE Database V5
Not known to be exploited · CVSS 5.0 Medium : upgrade to 4.0.0-beta.464 when convenient.
Data as of 13 Nov 2026, 23:53 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.0.0-beta.464
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Jun 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 13 Nov 2026.
What to do
Upgrade coollabsio coolify to 4.0.0-beta.464.
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.464 or later, where the vulnerability is fixed. Patch status is not explicitly confirmed beyond this version, so users should verify with vendor advisories for any further updates.
Description
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.464, `GET /api/v1/deployments/{uuid}` in DeployController.php retrieves deployment details without validating that the deployment belongs to the authenticated user's team. Any authenticated API user can read deployment records from other teams by providing a valid deployment UUID. This vulnerability is fixed in 4.0.0-beta.464.