# A few questions on CVE-2026-114952

**URL:** <https://forums.percona.com/t/a-few-questions-on-cve-2026-114952/41464>\
**Category:** MySQL & MariaDB\
**Created:** [November 20, 2026, 1:33am UTC](https://forums.percona.com/t/a-few-questions-on-cve-2026-114952/41464 "2026-11-20T01:33:38Z")\
**Posts on this page:** 4\
**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:** [November 20, 2026, 1:33am UTC](https://forums.percona.com/t/a-few-questions-on-cve-2026-114952/41464/1 "2026-11-20T01:33:39Z")

</div>

Hi everyone,

I’m trying to get a handle on **CVE-2026-114952** (MySQL “Client programs”, CVSS 9.1, CWE-287) and have a few questions:

1. **Percona exposure scope** : The official CVE only lists version ranges for Oracle MySQL Server/Cluster. Could someone confirm whether Percona Server, Percona XtraDBCluster are affected? If there’s a corresponding advisory or an affected-version list, a pointer would be much appreciated.

2. **Interim mitigations** : The vulnerability is described as being in “client programs”, yet the CVSS vector is `AV:N`, and the public info doesn’t really explain the attack path. Until a Percona patch is available, are there any hardening or workaround suggestions? For example, would enforcing TLS or restricting which servers clients can connect to actually help, or is patching the only real option?

---

<div class="post-metadata">

**Author:** ![hai.nguyen](https://avatars.discourse-cdn.com/v4/letter/h/41988e/32.png) [@hai.nguyen](https://forums.percona.com/u/hai.nguyen)\
**Post date:** [November 20, 2026, 2:49am UTC](https://forums.percona.com/t/a-few-questions-on-cve-2026-114952/41464/2 "2026-11-20T02:49:13Z")

</div>

Hi @ysysberserk2,

> 1. **Percona exposure scope** : The official CVE only lists version ranges for Oracle MySQL Server/Cluster. Could someone confirm whether Percona Server, Percona XtraDBCluster are affected? If there’s a corresponding advisory or an affected-version list, a pointer would be much appreciated.

Percona Server for MySQL and Percona XtraDB Cluster are built on the upstream MySQL Community releases. So they should be treated as affected.

There is no separate Percona advisory yet. The work for the fix are tracked here: [https://perconadev.atlassian.net/browse/PS-12162](https://perconadev.atlassian.net/browse/PS-12162)

> 1. **Interim mitigations** : The vulnerability is described as being in “client programs”, yet the CVSS vector is `AV:N`, and the public info doesn’t really explain the attack path. Until a Percona patch is available, are there any hardening or workaround suggestions? For example, would enforcing TLS or restricting which servers clients can connect to actually help, or is patching the only real option?

Oracle has not published the root cause, the affected binaries, the attack path, or a workaround. So there is no confirmed mitigation for this CVE yet. For now, we recommend the usual hardening:

- Restrict network access to the MySQL port to the hosts that need it
- Follow least-privilege practices: grant accounts only the privileges they need, and restrict them to specific hosts instead of ‘%’.
- Use encrypted connections (TLS)

These steps reduce exposure, but they are not a fix. Patching will be the only real option once a fixed version is released.

---

<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:** [November 20, 2026, 3:30am UTC](https://forums.percona.com/t/a-few-questions-on-cve-2026-114952/41464/3 "2026-11-20T03:30:51Z")

</div>

Thanks for your reply.

I noticed that the CVE lists **MySQL Cluster 8.0.0–8.0.50** as affected. Does that mean **Percona XtraDB Cluster 8.0.x** is affected as well?

Also, since **8.0 is now end-of-life** , does that mean those versions will **never receive a patch** , and the only way to resolve it is to **upgrade to 8.4.x**?

---

<div class="post-metadata">

**Author:** ![hai.nguyen](https://avatars.discourse-cdn.com/v4/letter/h/41988e/32.png) [@hai.nguyen](https://forums.percona.com/u/hai.nguyen)\
**Post date:** [November 20, 2026, 3:48am UTC](https://forums.percona.com/t/a-few-questions-on-cve-2026-114952/41464/4 "2026-11-20T03:48:26Z")

</div>

> I noticed that the CVE lists **MySQL Cluster 8.0.0–8.0.50** as affected. Does that mean **Percona XtraDB Cluster 8.0.x** is affected as well?

MySQL Cluster (also known as NDB Cluster) is a separate product from Oracle for clustered deployments using the NDB storage engine. Percona XtraDB Cluster 8.0 is built on Percona Server for MySQL 8.0, which is based on MySQL Server 8.0, not on MySQL Cluster 8.0.

Oracle lists only the versions it still supports, and MySQL Server 8.0 reached end of life in April 2026. Its absence from the list does not mean it is unaffected.

Since no fixed release has been published yet, we cannot review the code to confirm whether MySQL Server 8.0 is affected. If it is, Percona Server for MySQL 8.0 and Percona XtraDB Cluster 8.0 are affected as well.

> Also, since **8.0 is now end-of-life** , does that mean those versions will **never receive a patch** , and the only way to resolve it is to **upgrade to 8.4.x**?

For MySQL Community 8.0, yes: Oracle will not ship further 8.0 releases after 8.0.46.

For Percona Server for MySQL 8.0 and Percona XtraDB Cluster 8.0, Percona offers post-EOL support that includes backported security fixes: [https://www.percona.com/mysql-8-0-eol-support](https://www.percona.com/mysql-8-0-eol-support)
