CVE-2026-57498

CRITICALPre-NVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 87% 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.474, Coolify's API controllers consistently validate server ownership with Server::whereTeamId($teamId) before any operation. However, multiple Livewire web UI components accept server_id and destination_uuid from URL query parameters without any team ownership validation, allowing cross-team resource deployment. This vulnerability is fixed in 4.0.0-beta.474.

CVSS v3
9.6
EG Score
9.6(medium)
EPSS
12.8%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated Jun 29, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Cross-Team IDOR: Livewire Components Accept Unscoped server_id and destination_uuid — Deploy to Other Teams' Servers · Advisory · coollabsio/coolify · GitHub

https://github.com/coollabsio/coolify/security/advisories/GHSA-725v-f5gh-22q9

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 51× in last 7d / 96× 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.

  1. 2026-07-13 06:40 UTCEG score recompute
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-13 02:14 UTCEG score recompute
  5. 2026-07-12 21:51 UTCEG score recompute
  6. 2026-07-12 17:28 UTCEG score recompute
  7. 2026-07-12 13:04 UTCEG score recompute
  8. 2026-07-12 08:40 UTCEG score recompute
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-12 04:16 UTCEG score recompute
  11. 2026-07-11 23:51 UTCEG score recompute
  12. 2026-07-11 19:27 UTCEG score recompute
  13. 2026-07-11 15:03 UTCEG score recompute
  14. 2026-07-11 10:38 UTCEG score recompute
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-11 06:13 UTCEG score recompute
  18. 2026-07-11 01:46 UTCEG score recompute
  19. 2026-07-10 21:20 UTCEG score recompute
  20. 2026-07-10 16:57 UTCEG score recompute
  21. 2026-07-10 12:33 UTCEG score recompute
  22. 2026-07-10 08:07 UTCEG score recompute
  23. 2026-07-10 03:44 UTCEG score recompute
  24. 2026-07-09 23:14 UTCEG score recompute
  25. 2026-07-09 19:10 UTCEPSS rescore
Show 71 more
  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-09 18:50 UTCEG score recompute
  3. 2026-07-09 14:27 UTCEG score recompute
  4. 2026-07-09 09:57 UTCEG score recompute
  5. 2026-07-09 05:34 UTCEG score recompute
  6. 2026-07-09 01:10 UTCEG score recompute
  7. 2026-07-08 20:45 UTCEG score recompute
  8. 2026-07-08 16:20 UTCEG score recompute
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-08 11:56 UTCEG score recompute
  12. 2026-07-08 07:15 UTCEG score recompute
  13. 2026-07-08 02:41 UTCEG score recompute
  14. 2026-07-07 22:17 UTCEG score recompute
  15. 2026-07-07 17:53 UTCEG score recompute
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 13:30 UTCEG score recompute
  19. 2026-07-07 09:05 UTCEG score recompute
  20. 2026-07-07 04:41 UTCEG score recompute
  21. 2026-07-07 00:15 UTCEG score recompute
  22. 2026-07-06 19:51 UTCEG score recompute
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 15:28 UTCEG score recompute
  26. 2026-07-06 11:00 UTCEG score recompute
  27. 2026-07-06 06:19 UTCEG score recompute
  28. 2026-07-06 02:23 UTCEPSS rescore
  29. 2026-07-06 02:23 UTCEPSS rescore
  30. 2026-07-06 01:55 UTCEG score recompute
  31. 2026-07-05 21:31 UTCEG score recompute
  32. 2026-07-05 17:07 UTCEG score recompute
  33. 2026-07-05 12:44 UTCEG score recompute
  34. 2026-07-05 08:18 UTCEG score recompute
  35. 2026-07-05 03:54 UTCEG score recompute
  36. 2026-07-05 02:31 UTCEPSS rescore
  37. 2026-07-05 02:30 UTCEPSS rescore
  38. 2026-07-04 23:23 UTCEG score recompute
  39. 2026-07-04 18:59 UTCEG score recompute
  40. 2026-07-04 14:36 UTCEG score recompute
  41. 2026-07-04 10:13 UTCEG score recompute
  42. 2026-07-04 06:31 UTCEPSS rescore
  43. 2026-07-04 06:31 UTCEPSS rescore
  44. 2026-07-04 05:49 UTCEG score recompute
  45. 2026-07-04 01:24 UTCEG score recompute
  46. 2026-07-03 21:00 UTCEG score recompute
  47. 2026-07-03 16:37 UTCEG score recompute
  48. 2026-07-03 12:13 UTCEG score recompute
  49. 2026-07-03 07:46 UTCEG score recompute
  50. 2026-07-03 03:21 UTCEG score recompute
  51. 2026-07-02 22:58 UTCEG score recompute
  52. 2026-07-02 18:33 UTCEG score recompute
  53. 2026-07-02 14:10 UTCEG score recompute
  54. 2026-07-02 09:47 UTCEG score recompute
  55. 2026-07-02 05:24 UTCEG score recompute
  56. 2026-07-02 01:00 UTCEG score recompute
  57. 2026-07-01 20:34 UTCEG score recompute
  58. 2026-07-01 16:11 UTCEG score recompute
  59. 2026-07-01 15:07 UTCEPSS rescore
  60. 2026-07-01 11:48 UTCEG score recompute
  61. 2026-07-01 07:25 UTCEG score recompute
  62. 2026-07-01 03:01 UTCEG score recompute
  63. 2026-06-30 23:22 UTCEPSS rescore
  64. 2026-06-30 22:37 UTCEG score recompute
  65. 2026-06-30 18:14 UTCEG score recompute
  66. 2026-06-30 13:50 UTCEG score recompute
  67. 2026-06-30 09:26 UTCEG score recompute
  68. 2026-06-30 05:03 UTCEG score recompute
  69. 2026-06-30 00:40 UTCEG score recompute
  70. 2026-06-29 20:17 UTCEG score recompute
  71. 2026-06-29 20:17 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57498?
CVE-2026-57498 is a critical vulnerability published on June 29, 2026. Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.474, Coolify's API controllers consistently validate server ownership with Server::whereTeamId($teamId) before any operation. However, multiple Livewire web UI components accept…
When was CVE-2026-57498 disclosed?
CVE-2026-57498 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57498 actively exploited?
CVE-2026-57498 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57498?
CVE-2026-57498 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-57498?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57498, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-57498

Explore →

Is Your Infrastructure Affected by CVE-2026-57498?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs