View a markdown version of this page

Aurora MySQL database engine updates 2026-10-05 (version 3.10.6, compatible with MySQL 8.0.42) - Amazon Aurora
Improvements

Aurora MySQL database engine updates 2026-10-05 (version 3.10.6, compatible with MySQL 8.0.42)

Version: 3.10.6

Aurora MySQL 3.10.6 is generally available. Aurora MySQL 3.10 versions are compatible with MySQL 8.0.42. For more information about the community changes, see MySQL 8.0 Release Notes on the MySQL website.

For details of the new features in Aurora MySQL version 3, see Aurora MySQL version 3 compatible with MySQL 8.0. For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see Comparison of Aurora MySQL version 2 and Aurora MySQL version 3. For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see Comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition in the Amazon Aurora User Guide.

You can perform an in-place upgrade using Zero Downtime Patching (ZDP), restore a snapshot, or initiate a managed blue/green upgrade using Amazon RDS Blue/Green Deployments from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.10.6 cluster.

For information about planning an upgrade to Aurora MySQL version 3, see Planning a major version upgrade for an Aurora MySQL cluster. For general upgrade information, see Upgrading Aurora MySQL DB clusters in the Amazon Aurora User Guide.

For troubleshooting information, see Troubleshooting for Aurora MySQL in-place upgrade in the Amazon Aurora User Guide.

If you have any questions or concerns, Support is available on the community forums and through Support. For more information, see Maintaining an Aurora DB cluster in the Amazon Aurora User Guide.

Improvements

Security fixes

  • Fixed an issue which can cause a database instance to restart when setting up Kerberos Service Principal Name.

  • Fixed an issue where queries run through prepared statements could generate duplicate entries in the advanced audit log.

  • Fixed an issue where the Advanced Audit log recorded an incorrect user and host for SQL statements executed inside a SQL SECURITY DEFINER routine (stored procedure, function, or trigger). These records showed the routine's definer user and host (for example, 'user'@'%') instead of the SQL client that invoked the routine. After this fix, the records show the user and host of the invoking SQL client.

This release includes fixes for the following high severity CVEs:

Availability improvements

  • Fixed an issue that could cause an additional restart during Zero-downtime patching (ZDP) impacting the overall patching time and ability to preserve connections.

  • Fixed an issue where excessively large thread_stack configurations could prevent the Aurora MySQL server from starting during a restart or upgrade. Aurora MySQL server now automatically resets thread_stack to the engine default value (1 MB) when it exceeds system memory, preventing startup failures.

  • Fixed a memory management issue that could cause a reader instance to restart when processing write workloads through write forwarding.

  • Fixed an issue that could cause write forwarding on a reader DB instance to stop working, requiring a reboot of the reader to restore write forwarding. This could occur when a forwarded query was cancelled or timed out while using global write forwarding or local write forwarding.

  • Fixed an issue that could make the replica briefly disconnect and reconnect to the primary, causing a temporary spike in replication lag (AuroraReplicaLag).

  • Fixed an issue which can cause the writer instance to restart while processing ALTER TABLE ... REORGANIZE PARTITION SQL statement that changes sub-partition order.

General improvements

  • Fixed an issue where, during write forwarding, a reader instance restart could leave an orphan forwarding session on the writer instance, and killing that session could cause the writer to restart.

  • Fixed an issue where graceful reader disconnections could incorrectly increment Aborted_clients on the writer instance when write forwarding is enabled.

  • Fixed an issue where, with write forwarding enabled, a reader session with aurora_replica_read_consistency set to global could fail to read the latest committed changes.

  • Fixed an issue that can cause the AuroraReplicaLag metric to report values higher than the true replica lag on DB clusters that have enhanced binlog enabled and little to no write workload.

Integration of MySQL community edition bug fixes

  • Events created within stored programs were not always handled correctly. (Bug#36402968)

  • Fixed an issue where renaming a column using ALTER TABLE ... CHANGE COLUMN, on a table with prior instant DDL changes, could result in incorrect internal column-position metadata. (Bug#38935534)