PXC-4934 [Doc] Release notes for - PXC 8.4.10

docs/release-notes/8.4.10-10.md

@@ -0,0 +1,106 @@
+# Percona XtraDB Cluster 8.4.10-10 (2026-07-23)
+
+!!! note ""
+
+    Percona XtraDB Cluster 8.4.9-9 was not released; 8.4.10-10 is the next build in this series. This release includes enhancements and bug fixes from MySQL 8.4.9 and MySQL 8.4.10.
+
+Percona XtraDB Cluster (PXC) supports critical business applications in both cloud and on-premises environments, including public, private, and hybrid setups. Our free, open source, enterprise-grade solution includes the high availability and security features your business requires to meet your customer expectations and business goals.
+
+Percona XtraDB Cluster 8.4.10-10 is based on Percona Server for MySQL and includes all improvements and bug fixes available in the [Percona Server for MySQL 8.4.10-10 (2026-06-30) release notes](https://docs.percona.com/percona-server/8.4/release-notes/8.4.10-10.html).
+
+## Release highlights
+
+### Percona Server for MySQL 8.4.10-10
+
+Percona Server for MySQL 8.4.10-10 introduces the following new features and improvements:
+
+* Integrates the new Key Management Interoperability Protocol (KMIP) library into the key management component.
+
+* Adds JSONL (JSON Lines) output format for Audit Log Filter.
+
+* Increases the verbosity of the data dictionary upgrade process, making it easier to diagnose issues that occur during upgrade.
+
+* Logs SQL statements for the Audit Log Filter `table_access` class and the `read` and `insert` subclasses.
+
+* Flushes the audit log buffer on server shutdown when the `ASYNCHRONOUS` logging strategy is in use, preventing the loss of buffered events.
+
+* Reduces memory pressure in the Audit Log Filter component caused by VFS buffering.
+
+* Aligns the `audit_log_filter.format=NEW` output between the 8.0 plugin and the 8.4 component.
+
+* Optimizes performance for `mem_root_deque`.
+
+### MySQL 8.4.10
+
+Improvements and bug fixes provided by Oracle for MySQL 8.4.10 and included in Percona Server for MySQL are the following:
+
+* Connection attribute parsing could read a length-encoded size field before verifying that the complete field was present in the packet, leading to an out-of-bounds read. A size check is now performed before reading the field. (Bug #39116965)
+
+* A regression in row size estimation for `ROW_FORMAT=COMPRESSED` tables could cause `CREATE TABLE` to fail with `Row size too large` for tables that were accepted in earlier releases. (Bug #39129182, Bug #120323)
+
+Find the complete list of bug fixes and changes in the [MySQL 8.4.10 release notes](https://dev.mysql.com/doc/relnotes/mysql/8.4/en/news-8-4-10.html).
+
+## Security updates
+
+This release addresses the following security vulnerabilities:
+
+* [CVE-2026-46850](https://www.cve.org/CVERecord?id=CVE-2026-46850): A vulnerability in MySQL Shell (Shell for VS Code) allows a low-privileged attacker with network access via HTTP to compromise MySQL Shell, with potential scope change impact on additional products (CVSS 3.1 Base Score 9.9).
+
+* [CVE-2026-46860](https://www.cve.org/CVERecord?id=CVE-2026-46860): A vulnerability in MySQL Router allows an unauthenticated attacker with network access via HTTP to compromise MySQL Router (CVSS 3.1 Base Score 9.8).
+
+* [CVE-2026-46861](https://www.cve.org/CVERecord?id=CVE-2026-46861): A vulnerability in MySQL NDB Cluster (NDB Operator) allows a low-privileged attacker with network access via HTTP to access or modify critical data, with potential scope change impact (CVSS 3.1 Base Score 9.6).
+
+* [CVE-2026-46862](https://www.cve.org/CVERecord?id=CVE-2026-46862): A vulnerability in MySQL Router allows an unauthenticated attacker with network access via TLS to cause a hang or repeatable unexpected exit of MySQL Router (CVSS 3.1 Base Score 7.5).
+
+* [CVE-2026-46863](https://www.cve.org/CVERecord?id=CVE-2026-46863): A vulnerability in MySQL Server connection handling allows an unauthenticated attacker with network access via multiple protocols to cause a hang or repeatable unexpected exit of the server (CVSS 3.1 Base Score 7.5).
+
+* [CVE-2026-46869](https://www.cve.org/CVERecord?id=CVE-2026-46869): A vulnerability in MySQL Shell (Dump and Load) allows an unauthenticated attacker with network access to access critical data when user interaction is required (CVSS 3.1 Base Score 6.5).
+
+* [CVE-2026-46870](https://www.cve.org/CVERecord?id=CVE-2026-46870): A vulnerability in MySQL Shell (Shell for VS Code) allows a low-privileged attacker with network access to compromise MySQL Shell, with potential scope change impact (CVSS 3.1 Base Score 8.5).
+
+* [CVE-2026-46871](https://www.cve.org/CVERecord?id=CVE-2026-46871): A vulnerability in MySQL Shell (Shell for VS Code) allows a low-privileged attacker with network access via multiple protocols to access critical data (CVSS 3.1 Base Score 6.5).
+
+* [CVE-2026-48165](https://www.cve.org/CVERecord?id=CVE-2026-48165): A vulnerability in the handling of the `wsrep_sst_donor` and `wsrep_sst_receive_address` system variables allowed a high-privileged user to execute arbitrary shell commands with the privileges of the `mariadbd` process during State Snapshot Transfer (SST) due to improper input sanitization (CVSS 3.1 Base Score 7.2). :contentReference[oaicite:0]{index=0}. (This fix was backported from MariaDB. Thanks to the MariaDB project for identifying and fixing this issue.)
+
+* [CVE-2026-49261](https://www.cve.org/CVERecord?id=CVE-2026-49261): A vulnerability in MariaDB Server with `wsrep_notify_cmd` enabled allowed a remote attacker to execute arbitrary shell commands by embedding commands in the name of a joiner node due to improper input sanitization (CVSS 3.1 Base Score 10.0). :contentReference[oaicite:0]{index=0}. (This fix was backported from MariaDB. Thanks to the MariaDB project for identifying and fixing this issue.)
+
+## Bug fixes
+
+* [PXC-4683](https://perconadev.atlassian.net/browse/PXC-4683): Fixed an issue where a node could leave the cluster after an error in a stored procedure.
+
+* [PXC-4799](https://perconadev.atlassian.net/browse/PXC-4799): Fixed an issue where a backup node could fail with an `Inconsistency` error when a pending DDL operation conflicted with `FLUSH TABLES WITH READ LOCK` (FTWRL).
+
+* [PXC-4805](https://perconadev.atlassian.net/browse/PXC-4805): The `mysqlchk` script was missing from the Percona XtraDB Cluster 8.4 package and binary tarball distributions.
+
+* [PXC-4825](https://perconadev.atlassian.net/browse/PXC-4825): Fixed an issue where `performance_schema.variables_by_thread` did not include `wsrep` threads.
+
+* [PXC-4844](https://perconadev.atlassian.net/browse/PXC-4844): Fixed an issue where inconsistency voting under high load could trigger an internal deadlock and permanently pause Flow Control.
+
+* [PXC-4849](https://perconadev.atlassian.net/browse/PXC-4849): Fixed an issue where a node could fail to join the cluster after a successful State Snapshot Transfer (SST) because of an Event Scheduler task and the `read_only` setting.
+
+* [PXC-4887](https://perconadev.atlassian.net/browse/PXC-4887): Fixed an issue where `CREATE ROLE` statements were not replicated when the validate password plugin was enabled.
+
+* [PXC-4963](https://perconadev.atlassian.net/browse/PXC-4963): Fixed an issue where `GRANT` privileges differed between in-place upgraded and newly installed Percona XtraDB Cluster instances.
+
+* [PXC-5233](https://perconadev.atlassian.net/browse/PXC-5233): Fixed an issue where the Percona XtraDB Cluster 8.4 entrypoint invoked the removed `mysql_upgrade` binary, causing an unexpected exit loop during rolling upgrades from Percona XtraDB Cluster 8.0.
+
+* [PXC-5229](https://perconadev.atlassian.net/browse/PXC-5229): Fixed an issue where `WSREP` applier threads could inherit `tx_read_only=true`, causing replication failures and node inconsistency.
+
+## Builds and packaging
+
+* Percona XtraDB Cluster 8.4.10-10 adds support for Ubuntu 26.04.
+
+* Percona Server for MySQL releases include a mixture of PGO and non-PGO builds. Where Profile-Guided Optimization (PGO) is enabled, the compiler uses runtime profiling data from representative workloads to guide optimization, which can improve throughput and reduce latency compared with non-PGO builds.
+
+* See [Profile-Guided Optimization (PGO) and non-PGO builds](https://docs.percona.com/percona-server/8.4/pgo.html) for benefits, considerations, and which build you receive for your platform.
+
+## Useful links
+
+* The [Percona XtraDB Cluster installation instructions](https://www.percona.com/doc/percona-xtradb-cluster/8.4/install/index.html)
+
+* The [Percona XtraDB Cluster downloads](https://www.percona.com/mysql/software/percona-xtradb-cluster)
+
+* The [Percona XtraDB Cluster GitHub location](https://github.com/percona/percona-xtradb-cluster)
+
+* To contribute to the documentation, review the [Documentation Contribution Guide](https://github.com/percona/pxc-docs/blob/8.4/contributing.md)
+

docs/release-notes/release-notes_index.md

@@ -1,5 +1,7 @@
 # Percona XtraDB Cluster {{vers}} release notes index
 
+* [Percona XtraDB Cluster 8.4.10-10 (2026-07-23)](8.4.10-10.md)
+
 * [Percona XtraDB Cluster 8.4.8-8 (2026-04-15)](8.4.8-8.md)
 
 * [Percona XtraDB Cluster 8.4.7-7 (2026-01-13)](8.4.7-7.md)

docs/templates/pdf_cover_page.tpl

@@ -7,5 +7,5 @@
 {% if config.site_description %}
 <h1>{{ config.site_description }}</h1>
 {% endif %} 
-<h2>8.4.8-8 (April 15, 2026)</h2>
+<h2>8.4.10-10 (July 23, 2026)</h2>
 <!--<h3>Percona Technical Documentation Team</h3>-->

mkdocs-base.yml

@@ -174,6 +174,7 @@ nav:
   - get-help.md
   - Release notes:
       - Release notes index: release-notes/release-notes_index.md
+      - release-notes/8.4.10-10.md
       - release-notes/8.4.8-8.md
       - release-notes/8.4.7-7.md
       - release-notes/8.4.6-6.md

variables.yml

@@ -1,9 +1,9 @@
 # variables for HTML output
 
-release: '8.4.8-8'
+release: '8.4.10-10'
 version: '8.4'
 vers: '8.4' # we are going to use it instead of version
 pkg: 'pxc-84-lts'
-release_date: '2026-04-15'
-title_date: '2026-04-15'
+release_date: '2026-07-23'
+title_date: '2026-07-23'