Join our Newsletter — 33% off our NHI Course
Home› Guides› MySQL 8.0 End of Life Guide: Upgrade Paths…
Guide Vulnerability Management

MySQL 8.0 End of Life Guide: Upgrade Paths and Security Risk After April 2026

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 18 November 2026 15 min read
On this page

MySQL 8.0 left Oracle's active support window in April 2026, so every 8.0 server you still run is now a database that will not receive the routine security fixes your patch programme assumes. This guide explains what the change means in practice, which upgrade paths Oracle supports, which 8.4 LTS changes break applications and service accounts, and how to run the move without losing control of the identities that connect to your databases.

Status as of 17 Nov 2026: Oracle's MySQL Product Support EOL Announcements page states that, per Oracle's Lifetime Support policy, as of 21 April 2026 MySQL 8.0 is covered under Oracle Sustaining Support, and recommends moving to 8.4 LTS or 9.7 LTS. Check that page for later changes before you set dates in a plan.

For the wider decision framework on upgrade, extended support, isolation or retirement, see the Operating System End of Life and Extended Support Guide. For hardening the version you move to, see the MySQL Security Guide. This page stays on the MySQL 8.0 transition itself.

Key takeaways

  • MySQL 8.0 is in Sustaining Support from 21 April 2026. Under Oracle's Lifetime Support model, Sustaining Support is the phase after Premier and Extended Support; plan as if no new 8.0 fixes will arrive.
  • The supported next stop is 8.4 LTS. Oracle's upgrade path table lists 8.0.37 to 8.4.x LTS as supported by in-place upgrade, logical dump and load, or replication. Skipping an LTS series is not supported.
  • 9.7 LTS is reached through 8.4. Oracle documents upgrades between consecutive LTS series, such as 8.4.x to 9.7.x, so a 9.7 target still means passing through 8.4 first.
  • 8.4 changes authentication defaults. The mysql_native_password plugin is no longer enabled by default, and default_authentication_plugin is removed. Old service accounts and connectors are the most common breakage.
  • Removed options can stop a server starting. --ssl, --admin-ssl, --skip-host-cache and the keyring_file plugin are gone in 8.4. Audit configuration files before the upgrade window.
  • Run the MySQL Shell Upgrade Checker first. Oracle recommends it before any upgrade, and it turns a risky cutover into a list of findings you can fix in advance.

What changed in April 2026

Oracle publishes MySQL lifecycle status on its product support end of life announcements page. As of 17 Nov 2026 that page says MySQL 8.0 is covered under Oracle Sustaining Support as of 21 April 2026. It also records an earlier notice, announced on 4 August 2023, that existing MySQL 8.0 would continue to provide 32-bit and 64-bit binaries for supported platforms until end of life in April 2026.

The same page carries platform notices that affect your target version as well as 8.0. Binary builds for Oracle Solaris end on 29 September 2026 across all MySQL versions and products, including the 8.4 LTS branch. Binary builds for Enterprise Linux 7 have ended for all release series, including 8.4 and 9.x, under an update dated 4 August 2026. From MySQL 8.1 onward Oracle provides only 64-bit binaries. If your 8.0 estate sits on Solaris, Enterprise Linux 7 or 32-bit hosts, the database upgrade is also an operating system project.

Sustaining Support is not the same as active support. In Oracle's Lifetime Support model it generally means continued access to existing fixes, documentation and help, without new fixes for newly found problems. For a security team the practical reading is simple: a vulnerability disclosed after April 2026 that affects 8.0 should be assumed to stay unfixed on 8.0. Confirm the terms of your own Oracle contract if you hold one, and do not plan around fixes the support phase does not promise.

Community Edition users have no contract to read. The binaries stop, the source tree for 8.0 stops moving, and the next MySQL Critical Patch Update will only list fixes for the supported series.

The MySQL release model you are moving into

MySQL 8.0 predates the current release model. Oracle's reference manual for 8.4 describes two tracks. Long-Term Support (LTS) releases are for environments that need stable features and a longer support period, and follow the Oracle Lifetime Support Policy, which includes 5 years of Premier Support and 3 years of Extended Support. Innovation releases give access to the latest features and are supported only until the next Innovation release. Oracle states that both tracks receive bug and security fixes and are production grade.

The behaviour rules matter more to operations than the support lengths. Within an LTS series there are no removals: features can be removed or added only in the first release of an LTS series, such as 8.4.0, and not later. Innovation releases are expected to change behaviour as code is refactored and deprecated functions are removed.

TrackSupportBehaviour changesFits
LTS (8.4, 9.7)Oracle Lifetime Support Policy: 5 years Premier, 3 years ExtendedOnly at the first release of the seriesProduction systems, regulated estates, vendor-certified applications
Innovation (9.x between LTS releases)Until the next Innovation releaseExpected between releasesTeams able to upgrade roughly quarterly and test each step

For most estates leaving 8.0, an LTS target is the safer default. An Innovation target commits you to a much faster upgrade cadence than 8.0 ever asked of you, and the teams still on 8.0 in late 2026 are usually the teams that find cadence hardest.

Supported upgrade paths

The upgrade paths table in the 8.4 reference manual is the authority here. The rows that matter for an 8.0 estate are these.

FromToSupported methods (per Oracle)Note
8.0.37 or later8.4.x LTSIn-place upgrade, logical dump and load, replicationBring older 8.0 builds up to a recent 8.0 release first
8.4.x LTS9.7.x LTSUpgrading to the next LTS series is supportedSkipping an LTS series is not supported
8.4.x9.x InnovationSupported before the next LTS seriesInnovation releases of different major versions cannot be upgraded directly
8.4.x LTSLater 8.4.xIn-place upgrades and downgrades within the seriesMySQL Clone is listed for moves within an LTS or Bugfix series

Two consequences follow. First, an estate on an old 8.0 build should patch forward within 8.0 before attempting 8.4, because the documented starting point is a recent 8.0 release. Second, a plan that says "go straight to 9.7" is really a two-hop plan: 8.0 to 8.4, then 8.4 to 9.7. Budget test cycles for both hops, or stop at 8.4 and schedule 9.7 later.

Oracle also states that a replication topology is upgraded with a rolling scheme in which each server is upgraded with one of the supported single-server methods. Downgrades from Innovation releases need a logical dump and load, so keep a tested logical backup whenever you step onto an Innovation release.

8.4 changes that break accounts and connections

The "What is new in MySQL 8.4" chapter lists the changes. The ones below touch authentication, transport security and keys, which is where identity and security teams get paged during upgrades.

Authentication

  • mysql_native_password is disabled by default. From 8.4.0 the deprecated plugin is not enabled unless you start the server with --mysql-native-password=ON or set mysql_native_password=ON in the [mysqld] section. Accounts still using it cannot log in after the upgrade until you migrate them or re-enable the plugin.
  • default_authentication_plugin is removed. Use authentication_policy, whose syntax has also changed. A configuration file that still sets the old variable needs editing before startup.
  • FIDO plugins are replaced. authentication_fido and authentication_fido_client are removed in favour of authentication_webauthn (an Enterprise Edition server plugin) and authentication_webauthn_client.
  • LDAP timeouts have new defaults. The authentication_ldap_simple_* and authentication_ldap_sasl_* connect and response timeouts default to 30 seconds.

The NHI Mgmt Group recommendation is to treat the plugin change as a forcing function, not an obstacle. Re-enabling mysql_native_password to make the upgrade pass carries a deprecated mechanism forward into a new LTS series. Instead, list every account by plugin, move service accounts to caching_sha2_password, confirm each client library and connector supports it, and rotate the credential at the same time. The How to rotate database credentials without downtime guide covers the dual-credential pattern that keeps applications running while you do it.

Privileges

8.4 adds finer privileges: FLUSH_PRIVILEGES, OPTIMIZE_LOCAL_TABLE and TRANSACTION_GTID_TAG. On upgrade Oracle grants them automatically to accounts that hold the related older privilege (for example, accounts with RELOAD receive FLUSH_PRIVILEGES when no account yet holds it). That keeps things working, but it also means your post-upgrade privilege review will see new grants nobody requested. Record them so they are not mistaken for tampering, then remove any that the account does not need.

The use of % and _ as wildcards in database-level grants is deprecated, and Oracle expects them to be treated as literals in a future release. Grants that rely on wildcard schema names are worth rewriting now, while you are already reviewing access.

Transport security

  • --ssl, --admin-ssl, have_ssl and have_openssl are removed. Use --tls-version and --admin-tls-version.
  • A new tls-certificates-enforced-validation option enforces certificate validation at startup and during ALTER INSTANCE RELOAD TLS, so an invalid certificate halts startup or is rejected at runtime.
  • --skip-host-cache is removed (use --host-cache-size=0) and FLUSH HOSTS is removed (use TRUNCATE TABLE performance_schema.host_cache).

Keys and encryption at rest

The keyring_file and keyring_encrypted_file plugins are removed in 8.4. Use component_keyring_file and component_keyring_encrypted_file. If you use InnoDB tablespace encryption on 8.0 with a keyring plugin, migrate the keyring to a component before the upgrade and prove you can still open encrypted tablespaces. A keyring that does not load means encrypted data that does not open, which turns an upgrade into a recovery incident. The Cryptographic Key Management Guide covers backup and escrow of the master key.

Replication and other removals

The old replication statements (CHANGE MASTER TO, START SLAVE, SHOW SLAVE STATUS, RESET MASTER and related) are removed in favour of the SOURCE and REPLICA forms. Monitoring scripts, runbooks and automation accounts that issue the old statements will fail. --innodb and --skip-innodb are removed, setting a startup option to NULL is rejected, and innodb_buffer_pool_in_core_file now defaults to OFF where supported, which keeps buffer pool contents out of core dumps.

Security risk of staying on 8.0

An unsupported database is not instantly breached. The risk grows over time, and it grows in predictable ways.

  • Unfixed vulnerabilities accumulate. Each quarterly Critical Patch Update that lists issues in supported MySQL series raises the question of whether 8.0 shares the code. Without a fix you are left with compensating controls.
  • Scanner findings become permanent. Vulnerability scanners and cloud posture tools flag end of life software as a finding in its own right. Expect this to surface in audits that reference vulnerability and patch management controls such as NIST SP 800-53 SI-2 (Flaw Remediation).
  • Old authentication stays in place. Estates that stay on 8.0 often keep accounts on mysql_native_password, shared application logins and long-lived passwords, because the upgrade was the event that would have forced change.
  • The platform underneath is often also ageing. The Enterprise Linux 7 and Solaris notices mean many 8.0 hosts sit on operating systems that are themselves out of support.
  • Connectors and drivers drift. Application teams upgrade client libraries over time; at some point the newest drivers stop being tested against 8.0, and pinning old drivers spreads the problem to application hosts.

Managed database services are a separate case. Cloud providers set their own end of standard support dates and extended support charges for MySQL 8.0 engines. Check your provider's current lifecycle page rather than assuming Oracle's dates apply unchanged.

Running the upgrade

  1. Inventory every 8.0 instance. Include replicas, disaster recovery copies, developer containers, appliance-embedded databases and managed instances. Record version, host operating system, owner and the applications that connect.
  2. Inventory the identities. For each instance, list accounts, authentication plugin, host patterns, privileges and the systems that use them. Service accounts are the connection you most need to keep working; the Database Credential and Access Security Guide explains the access model.
  3. Patch within 8.0. Bring each instance to a recent 8.0 release so it meets the documented 8.0.37 starting point.
  4. Run the Upgrade Checker. Oracle recommends the MySQL Shell Upgrade Checker Utility before any upgrade. Treat errors as blockers and warnings as work items with owners.
  5. Fix configuration. Remove or replace removed options (default_authentication_plugin, --ssl, --skip-host-cache, keyring plugins). Validate TLS certificates now, because 8.4 can refuse to start on a bad one.
  6. Migrate accounts off mysql_native_password. Test each connector against caching_sha2_password in staging, then move accounts and rotate credentials.
  7. Back up and prove restore. Take a full backup and a logical dump, and restore both to a scratch host. Keep keyring material with the backup plan; see the Database Backup Security Guide.
  8. Upgrade replicas first. Follow Oracle's rolling scheme for replication topologies and promote an upgraded replica when it has run cleanly.
  9. Review after cutover. Compare privileges before and after, document the automatically added privileges, and confirm audit logging still runs.

Where an instance cannot be upgraded quickly, for example because a vendor has not certified its application on 8.4, put it on a dated exception. Isolate it on the network, restrict which hosts and accounts can connect, remove interactive human access, and log every connection. Record the exception owner and the vendor's committed certification date.

Where identity fits

Most connections to a production MySQL server are made by non-human identities: application service accounts, replication users, backup agents, monitoring collectors, ETL jobs and, increasingly, AI agents and data tools. These accounts are created once and rarely revisited, so they carry the most legacy: old plugins, broad host patterns such as '%', and passwords that predate current staff.

An end of life upgrade is one of the few moments when every one of those accounts must be touched. Use it to:

  • Assign a named owner to every service account and remove those with no owner and no recent logins.
  • Replace wildcard host patterns with the specific hosts or subnets that connect.
  • Split shared application logins so each application has its own account and privileges.
  • Move credentials into a secrets manager and set a rotation interval.
  • Require TLS for service accounts with REQUIRE SSL or stronger, now that 8.4 validates certificates at startup.

Detection and measurement

Track the programme with a small set of measures that can be pulled from inventory and from the servers themselves.

  • Count of MySQL 8.0 instances, by environment, with a target date for zero in production.
  • Count of accounts by authentication plugin, from mysql.user, with mysql_native_password trending to zero.
  • Count of accounts with '%' host patterns and with global privileges.
  • Instances on operating systems that are out of support, from the same inventory.
  • Open exceptions, each with an owner and a date.

During cutover, watch for spikes in authentication failures (error log and performance schema connection errors). A sudden rise after an upgrade usually means a client still using mysql_native_password or an old driver. Investigate it before you re-enable the deprecated plugin.

Common failure patterns

  • Re-enabling mysql_native_password permanently to make the upgrade pass, so the deprecated mechanism carries into a new LTS series.
  • Planning a direct 8.0 to 9.7 jump, then discovering mid-project that skipping 8.4 is not a supported path.
  • Losing the keyring during the move from keyring plugins to components, leaving encrypted tablespaces unreadable.
  • Forgetting replicas and disaster recovery copies, so a forgotten 8.0 server becomes the weakest point in the estate.
  • Breaking monitoring and automation that still issue SHOW SLAVE STATUS or FLUSH HOSTS, and then running blind after cutover.
  • Treating auto-granted 8.4 privileges as unexplained changes, or the reverse, ignoring real unexplained grants because "the upgrade did it".
  • Assuming a managed service follows Oracle's dates and being surprised by extended support charges or forced upgrades.

Practitioner checklist

  • Confirm current status on Oracle's MySQL end of life announcements page and record the date checked.
  • Inventory every MySQL 8.0 instance, including replicas, DR, containers and managed services.
  • Patch each instance to a recent 8.0 release (8.0.37 or later) before the 8.4 upgrade.
  • Run the MySQL Shell Upgrade Checker and close all errors.
  • Remove default_authentication_plugin, --ssl, --admin-ssl, --skip-host-cache and keyring plugins from configuration.
  • Migrate every account off mysql_native_password and rotate its credential.
  • Migrate keyring plugins to components and test opening encrypted tablespaces.
  • Validate TLS certificates before the upgrade window.
  • Update scripts that use removed replication statements.
  • Take and test-restore a full backup and a logical dump.
  • Document auto-granted privileges and review all privileges after cutover.
  • Put any remaining 8.0 instance on a dated, owned, isolated exception.

Standards and references

Related NHI Mgmt Group resources: Operating System End of Life and Extended Support Guide · MySQL Security Guide · Database Patching · Database Credential and Access Security Guide

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 18 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org