The October 2026 MySQL releases are now available, including:
- MySQL 26.10 Innovation
- MySQL 9.7.4 LTS
- MySQL 8.4.13 LTS
MySQL 26.10 brings additional capabilities to Community Edition, new options for building REST applications, and improvements to database operations and developer tools. MySQL 9.7.4 and MySQL 8.4.13 continue maintenance updates for the supported LTS release lines.
October MySQL Server releases
MySQL 26.10 Innovation delivers new functionality and fixes. The MySQL 9.7.4 LTS and MySQL 8.4.13 LTS maintenance releases provide fixes for their respective release lines. Review the release notes for the complete changes and compatibility considerations for each version.
MySQL 26.10 Innovation highlights
Health Monitor in Community Edition
MySQL 26.10 brings the Health Monitor component to Community Edition, making system resource monitoring and disk forecasting available directly from MySQL Server. Administrators can inspect disk, memory, CPU, and MySQL process information through Performance Schema, with error log messages and diagnostic reports providing additional operational context.
Health Monitor exposes current and historical resource data, along with disk forecast samples and a forecast summary. This gives DBAs SQL-accessible information for investigating resource pressure and planning storage capacity.
The first Community release supports Linux and basic macOS resource collection. macOS provides memory, filesystem usage, and CPU information; metrics without a supported equivalent are exposed as NULL. Windows is outside the scope of this initial release.
By default, the component monitors the filesystem containing the MySQL data directory. Low disk space fencing is disabled by default: monitoring, warnings, and forecasting continue without placing the server into offline or super-read-only mode. Administrators can explicitly enable fencing when it fits their operational policy.
Health Monitor community proposal | Join the discussion
WebAuthn authentication in Community Edition
The authentication_webauthn server plugin moves to MySQL Community Edition for Innovation releases. It supports authentication with FIDO devices for multifactor authentication and passwordless access, expanding the security options available to Community users.
Review client compatibility and device registration requirements when planning adoption.
WebAuthn registration and usage background in MySQL 9.7
MySQL REST Service as a server component
MySQL REST Service can now run as a MySQL Server component. Applications can use HTTPS endpoints directly from MySQL Server without deploying a separate MySQL Router process for the REST service.
The component provides configuration variables for the HTTPS port, TLS certificate and key, worker threads, connection limits, and request and response sizes. SQL functions start, stop, and restart the service, while status variables report its runtime state. These controls give administrators a direct way to configure and observe the service within MySQL.
MySQL REST Service 26.10 documentation
More visibility into partition pruning
EXPLAIN FORMAT=TREE, supported EXPLAIN ANALYZE plans, and JSON format version 2 now show selected partitions on the relevant table-access nodes. Developers and DBAs can inspect the result of explicit partition restrictions and optimizer partition pruning alongside the execution plan.
For example, a range scan restricted to partition p1 can show “in partitions (p1)” in TREE output, while JSON v2 provides a structured partitions array. The list describes the plan’s selected read partitions; it is not a measurement of partitions physically visited during execution. This improves diagnostic visibility without changing partition pruning or query execution.
Partition pruning visibility community proposal
Finer control for JSON Duality Views
JSON Duality Views gain table- and column-level CHECK and NO CHECK annotations, together with column-level UPDATE and NO UPDATE controls.
CHECK and NO CHECK determine whether values participate in the document’s ETAG calculation for optimistic concurrency checking. Column settings override the table setting, allowing applications to exclude selected fields from conflict detection. UPDATE and NO UPDATE determine whether individual fields can be changed through the duality view.
These controls help developers align document updates and concurrency checks with application requirements. For example, a frequently changing informational field can be excluded from ETAG calculation when it should not cause a conflict with a business-data update.
JSON Duality Views background | CHECK and UPDATE controls proposal
InnoDB redo processing
InnoDB improves redo log parsing by caching the internal index metadata objects used to interpret index-record changes. Reusing parsed metadata reduces repeated construction of temporary index descriptions in this processing path. The change targets redo parsing efficiency; the benefit depends on the workload and redo being processed.
Explore the MySQL Server source
Support for four part version numbers
MySQL Server adds an update component to identify separately delivered updates on the same patch line. The full release identity uses MAJOR.MINOR.PATCH.UPDATE, allowing support teams and automation to distinguish exact delivered versions.
The new VERSION_WITH_UPDATE() function and read-only global version_with_update variable expose the full version. Existing VERSION() and @@version output retain their three-part compatibility format, and existing numeric compatibility identifiers keep their established meaning. The mysql_upgrade_history file also records exact update history.
MySQL clients tools and connectors
MySQL Router
MySQL Router can reload certificates, private keys, CA files, and certificate revocation lists from their configured paths without restarting the Router process. Existing sessions stay connected; subsequent TLS handshakes use the new material after a successful reload.
Administrators request the operation with mysqlrouter –reload-tls and the platform-specific target for the running instance. If replacement material is invalid, the affected TLS owner retains its previous working TLS state. This operation reloads TLS material, not the Router configuration file, and does not change existing sessions or TLS passthrough connections.
MySQL Shell
MySQL Shell exposes post-quantum TLS options with OpenSSL 3.5 or later for both Classic Protocol and X Protocol connections. The tls-kex, force-pqc, and use-pqc-sign options are accepted through the command line, connection URIs, and connection dictionaries. When the server provides the information, Shell status output reports the negotiated key-exchange and signature algorithms.
For Classic Protocol connections, Shell connection dictionaries add password1, password2, and password3 fields. Applications can supply or request passwords for the required factors through shell.connect(), shell.openSession(), and mysql.getSession(), with corresponding credential-helper support. These MFA password fields are not added to connection URIs.
The gui_plugin and migration_plugin are removed from the core command-line mysql-shell packages as the previous Shell GUI offering is superseded by MySQL Workbench. Review workflows that depend on these bundled plugins before upgrading.
MySQL Shell manual | MySQL Shell on GitHub
MySQL Workbench
Workbench adds an Error Log page with pagination, filtering, refresh, and export. Active connections can read performance_schema.error_log; local connections can also use the traditional-format error log file, including from an offline administration workspace when the saved file source is available.
Connection and user editors add non-password authentication and MFA configuration for up to three factors, with method-specific options and visible WebAuthn prompts. The update also adds WebAuthn device registration and password reset flows, including retaining or discarding an old password where supported. Authentication methods remain subject to server edition, platform, and client support.
MySQL Workbench 26 source and contribution information
MySQL Connectors
Connector/J updates third-party libraries and tooling, including dependencies used for OCI authentication, OpenTelemetry, and Protocol Buffers. Connector/Python updates and aligns third-party dependencies used across its supported capabilities.
Connector/J documentation | Connector/J on GitHub | Connector/Python documentation | Connector/Python on GitHub
Connector/C++ removes the mysql-connector-c++-compat RPM package, which supplied legacy compatibility libraries for the pre-9.0 ABI. Applications that depend on that ABI need an appropriate older package or a rebuild against a supported Connector/C++ ABI before upgrading. Regular Connector/C++ APIs are not changed by this packaging removal.
Connector/C++ documentation | Connector/C++ on GitHub
Clients, tools, and connectors support multiple MySQL Server versions. Select the latest compatible version for your deployment and review each product’s release notes for supported platforms, dependencies, and behavior changes.
Upgrade guidance
Choose the release track that fits your application and operational requirements:
- For the newest functionality and a regular upgrade cadence, evaluate MySQL 26.10.0 Innovation.
- For deployments using MySQL 9.7 LTS, review and apply the 9.7.4 maintenance update.
- For deployments standardized on MySQL 8.4 LTS, review and apply the 8.4.13 maintenance update.
Before upgrading, review the release notes and supported upgrade paths, run the MySQL Shell Upgrade Checker where applicable, and validate application behavior and performance in a test environment.
MySQL Shell Upgrade Checker Utility
Join the MySQL community
Explore MySQL projects, share feedback, and join conversations about features and roadmap priorities through our GitHub repositories and MySQL Community Discussions.
MySQL on GitHub | MySQL Community | Community Discussions
Download MySQL
Visit MySQL Downloads to find Community and commercial releases and the associated clients, tools, and connectors.
As always, thank you for using MySQL.