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.
CVE-2026-34167
This medium-severity CVE scores 5.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.0
- EG Score
- 5.0(medium)
- EPSS
- 9.9%
- KEV
- Not listed
Published
July 6, 2026
Last Modified
July 8, 2026
Advisory Details (4)
Auto-updated Jul 8, 2026Cross-tenant activity log disclosure via unlocked Livewire property in ActivityMonitor · Advisory · coollabsio/coolify · GitHub
https://github.com/coollabsio/coolify/security/advisories/GHSA-962v-gxmw-56hcv4.0.0-beta.471
Patch available: coollabsio/coolify v4.0.0-beta.471
https://github.com/coollabsio/coolify/releases/tag/v4.0.0-beta.471refactor: simplify remote process chain and harden ActivityMonitor
Patch available: coollabsio/coolify v4.0.0-beta.471 (PR #9189 merged 2026-03-26)
https://github.com/coollabsio/coolify/pull/9189commit 2729dffb3e30 (coollabsio/coolify)
Patch available: coollabsio/coolify v4.0.0-beta.471 (contains commit 2729dffb3e30)
https://github.com/coollabsio/coolify/commit/2729dffb3e30167c1ffd642357b7e0bb99b7d180Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-12 07:47 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 05:47 UTCEG score recompute
- 2026-07-10 03:47 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 01:47 UTCEG score recompute
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-07 23:45 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 21:45 UTCEG score recompute
- 2026-07-06 21:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-34167?
When was CVE-2026-34167 disclosed?
Is CVE-2026-34167 actively exploited?
What is the CVSS score of CVE-2026-34167?
How do I remediate CVE-2026-34167?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-34167
Is Your Infrastructure Affected by CVE-2026-34167?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.