Skip to main content
VulnerabilityPublished Updated

CVE-2026-34044: coollabsio coolify · Insecure Direct Object Reference

Affects coollabsio coolifySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 4.0.0-beta.466 soon.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.0-beta.466
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Upgrade coollabsio coolify to 4.0.0-beta.466.

Affected software

ProductAffectedFixed in
coollabsiocoolifyAffected
  • <4.0.0-beta.466
Fixed in
  • 4.0.0-beta.466
GitHubcoollabsio/coolifypkg:github/coollabsio/coolifyOther threatsAffected
  • =4.0.0-beta.466
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.466 or later, where the issue is fixed by scoping resource lookups to the current team. No other mitigation or workaround is documented. Patch status is not explicitly stated but the fix is included in version 4.0.0-beta.466.

Description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.466, the Logs::mount() component looks up resources by UUID without scoping the lookup to the current team, allowing an authenticated user to access logs for applications owned by other teams by supplying a victim resource UUID. This issue is fixed in version 4.0.0-beta.466.

References

Community reviews

Loading reviews…