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.
CVE-2026-34044
This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.7
- EG Score
- 7.7(medium)
- EPSS
- 15.5%
- KEV
- Not listed
Published
July 7, 2026
Last Modified
July 9, 2026
Advisory Details (3)
Auto-updated Jul 7, 2026v4.0.0-beta.466
Patch available: coollabsio/coolify v4.0.0-beta.466
https://github.com/coollabsio/coolify/releases/tag/v4.0.0-beta.466commit 6fbb5e626a82 (coollabsio/coolify)
Patch available: coollabsio/coolify v4.0.0-beta.466 (contains commit 6fbb5e626a82)
https://github.com/coollabsio/coolify/commit/6fbb5e626a82c576ae7a1a08b4e1d16aee2e82edCross-team IDOR in logs component (resource lookup not team-scoped) · Advisory · coollabsio/coolify · GitHub
https://github.com/coollabsio/coolify/security/advisories/GHSA-565g-9j4m-wqmrWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× 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-13 00:51 UTCEG score recompute
- 2026-07-12 13:06 UTCEG score recompute
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 01:20 UTCEG score recompute
- 2026-07-11 13:35 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 01:49 UTCEG score recompute
- 2026-07-10 14:03 UTCEG score recompute
- 2026-07-10 02:16 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 14:30 UTCEG score recompute
- 2026-07-09 02:43 UTCEG score recompute
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 14:56 UTCEG score recompute
- 2026-07-08 03:08 UTCEG score recompute
- 2026-07-07 15:22 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 03:32 UTCEG score recompute
- 2026-07-07 03:31 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-34044?
When was CVE-2026-34044 disclosed?
Is CVE-2026-34044 actively exploited?
What is the CVSS score of CVE-2026-34044?
How do I remediate CVE-2026-34044?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-34044
Is Your Infrastructure Affected by CVE-2026-34044?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.