Skip to main content
VulnerabilityPublished Updated

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

Affects coollabsio coolifySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.0 Medium : upgrade to 4.0.0-beta.471 when convenient.

Data as of 18 Nov 2026, 20:25 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 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 18 Nov 2026.

What to do

Upgrade coollabsio coolify to 4.0.0-beta.471.

Affected software

ProductAffectedFixed in
coollabsiocoolifyAffected
  • <4.0.0-beta.471
Fixed in
  • 4.0.0-beta.471
GitHubcoollabsio/coolifypkg:github/coollabsio/coolifyOther threatsAffected
  • =4.0.0-beta.471
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 version 4.0.0-beta.471 or later, where this vulnerability is fixed. Patch status is not explicitly stated in vendor advisories, but the fix is included in 4.0.0-beta.471. Until upgrading, restrict authenticated user access to trusted parties only.

Description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.471, the ActivityMonitor Livewire component exposes a public $activityId property without Livewire's #[Locked] attribute. It loads activities via Activity::find($this->activityId) with no authorization or team scoping. Activity IDs are auto-incrementing integers. Any authenticated user can enumerate activity records across all teams and read the full command output from remote SSH processes, which may include secrets, configuration files, and infrastructure details. This issue is fixed in version 4.0.0-beta.471.

References

Community reviews

Loading reviews…