# When will XtraDB Cluster 8.4.11 be avaiable?

**URL:** <https://forums.percona.com/t/when-will-xtradb-cluster-8-4-11-be-avaiable/41217>\
**Category:** MySQL & MariaDB\
**Created:** [August 28, 2026, 11:21am UTC](https://forums.percona.com/t/when-will-xtradb-cluster-8-4-11-be-avaiable/41217 "2026-08-28T11:21:25Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![ysysberserk2](https://avatars.discourse-cdn.com/v4/letter/y/c89c15/32.png) [@ysysberserk2](https://forums.percona.com/u/ysysberserk2)\
**Post date:** [August 28, 2026, 11:21am UTC](https://forums.percona.com/t/when-will-xtradb-cluster-8-4-11-be-avaiable/41217/1 "2026-08-28T11:21:26Z")

</div>

We has updated our cluster to XtraDB Cluster 8.4.10. But the scaner of our customers found cve problems in 8.4.10 and request us to update to 8.4.11.

Since Percona Server for MySQL 8.4.11 is available now. Can we just use its code to replace the mysql code in XtraDB Cluster 8.4.10 to build a 8.4.11 version?

---

<div class="post-metadata">

**Author:** ![Wayne\_Leutwyler](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/wayne_leutwyler/32/20829_2.png) [@Wayne\_Leutwyler](https://forums.percona.com/u/Wayne_Leutwyler)\
**Post date:** [August 28, 2026, 12:09pm UTC](https://forums.percona.com/t/when-will-xtradb-cluster-8-4-11-be-avaiable/41217/2 "2026-08-28T12:09:25Z")

</div>

Percona Server and PXC use different binaries. You can’t build PXC based off of Percona Server.

---

<div class="post-metadata">

**Author:** ![ysysberserk2](https://avatars.discourse-cdn.com/v4/letter/y/c89c15/32.png) [@ysysberserk2](https://forums.percona.com/u/ysysberserk2)\
**Post date:** [August 28, 2026, 12:55pm UTC](https://forums.percona.com/t/when-will-xtradb-cluster-8-4-11-be-avaiable/41217/3 "2026-08-28T12:55:53Z")

</div>

Thanks for your answer.

Then what I can do is to wait for the release of XtraDB Cluster 8.4.11?

---

<div class="post-metadata">

**Author:** ![Vadim\_Yalovets](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/vadim_yalovets/32/43_2.png) [@Vadim\_Yalovets](https://forums.percona.com/u/Vadim_Yalovets)\
**Post date:** [August 28, 2026, 1:24pm UTC](https://forums.percona.com/t/when-will-xtradb-cluster-8-4-11-be-avaiable/41217/4 "2026-08-28T13:24:37Z")

</div>

> [@ysysberserk2](#):
>
> We has updated our cluster to XtraDB Cluster 8.4.10. But the scaner of our customers found cve problems in 8.4.10 and request us to update to 8.4.11.

Could you provide details of the CVEs found?

 ![Screenshot 2026-08-28 at 16.23.02](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/1/8/18f19c64fc8f9372c3d34d627e945ddc25b9940e.png)

---

<div class="post-metadata">

**Author:** ![ysysberserk2](https://avatars.discourse-cdn.com/v4/letter/y/c89c15/32.png) [@ysysberserk2](https://forums.percona.com/u/ysysberserk2)\
**Post date:** [August 28, 2026, 2:01pm UTC](https://forums.percona.com/t/when-will-xtradb-cluster-8-4-11-be-avaiable/41217/5 "2026-08-28T14:01:42Z")

</div>

The scanner is Nexpose. It just simply fetch the version 8.4.10 and provide the following cve for oracle mysql 8.4.10.

CVE-2026-46936  
CVE-2026-47012  
CVE-2026-47023  
CVE-2026-47052  
CVE-2026-47064  
CVE-2026-60145  
CVE-2026-60163  
CVE-2026-60177  
CVE-2026-60178  
CVE-2026-60182  
CVE-2026-60183  
CVE-2026-60184  
CVE-2026-60185  
CVE-2026-60186  
CVE-2026-60187  
CVE-2026-60188  
CVE-2026-60189  
CVE-2026-60190  
CVE-2026-60191  
CVE-2026-60315  
CVE-2026-60316  
CVE-2026-60331  
CVE-2026-60332  
CVE-2026-60585  
CVE-2026-60747  
CVE-2026-61081  
CVE-2026-61094  
CVE-2026-61096  
CVE-2026-61109

---

<div class="post-metadata">

**Author:** ![Evgeniy\_Patlan](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/evgeniy_patlan/32/41_2.png) [@Evgeniy\_Patlan](https://forums.percona.com/u/Evgeniy_Patlan)\
**Post date:** [September 3, 2026, 9:35am UTC](https://forums.percona.com/t/when-will-xtradb-cluster-8-4-11-be-avaiable/41217/6 "2026-09-03T09:35:28Z")

</div>

> [@ysysberserk2](#):
>
> CVE-2026-46936

Thanks for you information. Yes the only solution is to wait for the release.
