Oracle’s MySQL blog says MySQL 8.0 was scheduled for end of life in April 2026. For MySQL HeatWave, Oracle extended 8.0 support to April 2027 with only essential security patches, blocked new 8.0 instances, and will automatically upgrade remaining 8.0 instances to MySQL 8.4 LTS after April 2027.
\nOracle’s February 5, 2026 MySQL blog post says MySQL 8.0 is scheduled for end of life in April 2026, and that Oracle had previously announced automatic upgrades of MySQL HeatWave 8.0 instances to the latest supported 8.4 release after that date. It now extends support for 8.0 instances in MySQL HeatWave until April 2027.
\nDuring the extension, existing HeatWave 8.0 instances keep operating and receive critical security patches, with all 8.0 instances automatically upgraded to 8.0.46 in the June 2026 maintenance cycle and only essential OS and database security patches applied until April 2027. Creating new 8.0 instances, changing instance shapes and adding 8.0-based read replicas are not allowed, and restoring a backup produces an instance on the latest 8.4 version.
\nAfter April 2027, any remaining HeatWave 8.0 instances will be automatically upgraded to MySQL 8.4 LTS during their next maintenance window. Oracle advises customers to plan upgrades with its sales and support teams and says proactively upgrading to MySQL 8.4 ensures continued access to the latest features and stability.
\nUse this for any MySQL 8.0 deployment. The extension described applies to Oracle’s MySQL HeatWave service; self-managed servers and other providers’ MySQL services follow their own support terms, so confirm each one.
\nDSE recommends inventorying every MySQL 8.0 instance and scheduling tested upgrades to MySQL 8.4 LTS, starting with internet-facing applications. Confirm each application vendor supports 8.4, back up and test restores before upgrading, rehearse the upgrade on a copy, and restrict network access to any 8.0 server still waiting.
\nQuery each server’s version after the upgrade, confirm applications pass functional tests on 8.4, and recheck the inventory quarterly until no 8.0 instances remain.
\nOracle MySQL Blog — Extending MySQL 8.0 support in MySQL HeatWave (February 5, 2026). Reviewed October 18, 2026.
", "content_text": "Oracle’s MySQL blog says MySQL 8.0 was scheduled for end of life in April 2026. For MySQL HeatWave, Oracle extended 8.0 support to April 2027 with only essential security patches, blocked new 8.0 instances, and will automatically upgrade remaining 8.0 instances to MySQL 8.4 LTS after April 2027.\nSource facts\nOracle’s February 5, 2026 MySQL blog post says MySQL 8.0 is scheduled for end of life in April 2026, and that Oracle had previously announced automatic upgrades of MySQL HeatWave 8.0 instances to the latest supported 8.4 release after that date. It now extends support for 8.0 instances in MySQL HeatWave until April 2027.\nDuring the extension, existing HeatWave 8.0 instances keep operating and receive critical security patches, with all 8.0 instances automatically upgraded to 8.0.46 in the June 2026 maintenance cycle and only essential OS and database security patches applied until April 2027. Creating new 8.0 instances, changing instance shapes and adding 8.0-based read replicas are not allowed, and restoring a backup produces an instance on the latest 8.4 version.\nAfter April 2027, any remaining HeatWave 8.0 instances will be automatically upgraded to MySQL 8.4 LTS during their next maintenance window. Oracle advises customers to plan upgrades with its sales and support teams and says proactively upgrading to MySQL 8.4 ensures continued access to the latest features and stability.\nApplicability\nUse this for any MySQL 8.0 deployment. The extension described applies to Oracle’s MySQL HeatWave service; self-managed servers and other providers’ MySQL services follow their own support terms, so confirm each one.\nDSE recommendation\nDSE recommends inventorying every MySQL 8.0 instance and scheduling tested upgrades to MySQL 8.4 LTS, starting with internet-facing applications. Confirm each application vendor supports 8.4, back up and test restores before upgrading, rehearse the upgrade on a copy, and restrict network access to any 8.0 server still waiting.\nVerification\nQuery each server’s version after the upgrade, confirm applications pass functional tests on 8.4, and recheck the inventory quarterly until no 8.0 instances remain.\nOfficial reference\nOracle MySQL Blog — Extending MySQL 8.0 support in MySQL HeatWave (February 5, 2026). Reviewed October 18, 2026.", "content_markdown": "Oracle’s MySQL blog says MySQL 8.0 was scheduled for end of life in April 2026. For MySQL HeatWave, Oracle extended 8.0 support to April 2027 with only essential security patches, blocked new 8.0 instances, and will automatically upgrade remaining 8.0 instances to MySQL 8.4 LTS after April 2027.\n\n## Source facts\n\nOracle’s [February 5, 2026 MySQL blog post](https://blogs.oracle.com/mysql/extending-mysql-8-0-support-in-mysql-heatwave) says MySQL 8.0 is scheduled for end of life in April 2026, and that Oracle had previously announced automatic upgrades of MySQL HeatWave 8.0 instances to the latest supported 8.4 release after that date. It now extends support for 8.0 instances in MySQL HeatWave until April 2027.\n\nDuring the extension, existing HeatWave 8.0 instances keep operating and receive critical security patches, with all 8.0 instances automatically upgraded to 8.0.46 in the June 2026 maintenance cycle and only essential OS and database security patches applied until April 2027. Creating new 8.0 instances, changing instance shapes and adding 8.0-based read replicas are not allowed, and restoring a backup produces an instance on the latest 8.4 version.\n\nAfter April 2027, any remaining HeatWave 8.0 instances will be automatically upgraded to MySQL 8.4 LTS during their next maintenance window. Oracle advises customers to plan upgrades with its sales and support teams and says proactively upgrading to MySQL 8.4 ensures continued access to the latest features and stability.\n\n## Applicability\n\nUse this for any MySQL 8.0 deployment. The extension described applies to Oracle’s MySQL HeatWave service; self-managed servers and other providers’ MySQL services follow their own support terms, so confirm each one.\n\n## DSE recommendation\n\nDSE recommends inventorying every MySQL 8.0 instance and scheduling tested upgrades to MySQL 8.4 LTS, starting with internet-facing applications. Confirm each application vendor supports 8.4, back up and test restores before upgrading, rehearse the upgrade on a copy, and restrict network access to any 8.0 server still waiting.\n\n## Verification\n\nQuery each server’s version after the upgrade, confirm applications pass functional tests on 8.4, and recheck the inventory quarterly until no 8.0 instances remain.\n\n## Official reference\n\n[Oracle MySQL Blog — Extending MySQL 8.0 support in MySQL HeatWave (February 5, 2026)](https://blogs.oracle.com/mysql/extending-mysql-8-0-support-in-mysql-heatwave). Reviewed October 18, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/mysql-8-0-end-of-life-april-2026-upgrade-8-4-lts-heatwave-april-2027/", "url": "https://update.dsesecurity.com/updates/mysql-8-0-end-of-life-april-2026-upgrade-8-4-lts-heatwave-april-2027/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-18" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/mysql-8-0-end-of-life-april-2026-upgrade-8-4-lts-heatwave-april-2027/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "MySQL 8.0 was scheduled to reach end of life in April 2026: plan tested upgrades to MySQL 8.4 LTS", "item": "https://update.dsesecurity.com/updates/mysql-8-0-end-of-life-april-2026-upgrade-8-4-lts-heatwave-april-2027/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/mysql-8-0-end-of-life-april-2026-upgrade-8-4-lts-heatwave-april-2027/#article", "identifier": "https://update.dsesecurity.com/updates/mysql-8-0-end-of-life-april-2026-upgrade-8-4-lts-heatwave-april-2027/", "url": "https://update.dsesecurity.com/updates/mysql-8-0-end-of-life-april-2026-upgrade-8-4-lts-heatwave-april-2027/", "headline": "MySQL 8.0 was scheduled to reach end of life in April 2026: plan tested upgrades to MySQL 8.4 LTS", "description": "Oracle’s MySQL blog says MySQL 8.0 was scheduled for end of life in April 2026. For MySQL HeatWave, Oracle extended 8.0 support to April 2027 with only…", "abstract": "Oracle’s MySQL blog says MySQL 8.0 was scheduled for end of life in April 2026. For MySQL HeatWave, Oracle extended 8.0 support to April 2027 with only essential security patches, blocked new 8.0 instances, and will automatically upgrade remaining 8.0 instances to MySQL 8.4 LTS after April 2027.", "articleBody": "Oracle’s MySQL blog says MySQL 8.0 was scheduled for end of life in April 2026. For MySQL HeatWave, Oracle extended 8.0 support to April 2027 with only essential security patches, blocked new 8.0 instances, and will automatically upgrade remaining 8.0 instances to MySQL 8.4 LTS after April 2027.\nSource facts\nOracle’s February 5, 2026 MySQL blog post says MySQL 8.0 is scheduled for end of life in April 2026, and that Oracle had previously announced automatic upgrades of MySQL HeatWave 8.0 instances to the latest supported 8.4 release after that date. It now extends support for 8.0 instances in MySQL HeatWave until April 2027.\nDuring the extension, existing HeatWave 8.0 instances keep operating and receive critical security patches, with all 8.0 instances automatically upgraded to 8.0.46 in the June 2026 maintenance cycle and only essential OS and database security patches applied until April 2027. Creating new 8.0 instances, changing instance shapes and adding 8.0-based read replicas are not allowed, and restoring a backup produces an instance on the latest 8.4 version.\nAfter April 2027, any remaining HeatWave 8.0 instances will be automatically upgraded to MySQL 8.4 LTS during their next maintenance window. Oracle advises customers to plan upgrades with its sales and support teams and says proactively upgrading to MySQL 8.4 ensures continued access to the latest features and stability.\nApplicability\nUse this for any MySQL 8.0 deployment. The extension described applies to Oracle’s MySQL HeatWave service; self-managed servers and other providers’ MySQL services follow their own support terms, so confirm each one.\nDSE recommendation\nDSE recommends inventorying every MySQL 8.0 instance and scheduling tested upgrades to MySQL 8.4 LTS, starting with internet-facing applications. Confirm each application vendor supports 8.4, back up and test restores before upgrading, rehearse the upgrade on a copy, and restrict network access to any 8.0 server still waiting.\nVerification\nQuery each server’s version after the upgrade, confirm applications pass functional tests on 8.4, and recheck the inventory quarterly until no 8.0 instances remain.\nOfficial reference\nOracle MySQL Blog — Extending MySQL 8.0 support in MySQL HeatWave (February 5, 2026). Reviewed October 18, 2026.", "datePublished": "2026-10-18T21:01:37+00:00", "dateModified": "2026-10-18T22:22:09+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/mysql-8-0-end-of-life-april-2026-upgrade-8-4-lts-heatwave-april-2027/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/mysql-8-0-end-of-life-april-2026-upgrade-8-4-lts-heatwave-april-2027/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "MySQL 8.0 was scheduled to reach end of life in April 2026: plan tested upgrades to MySQL 8.4 LTS" }, "articleSection": [ "Cybersecurity", "IT" ], "keywords": [ "Cybersecurity", "IT", "Briefing", "Important priority" ], "genre": "Briefing", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 312, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Oracle MySQL Blog — Extending MySQL 8.0 support in MySQL HeatWave (February 5, 2026)", "url": "https://blogs.oracle.com/mysql/extending-mysql-8-0-support-in-mysql-heatwave" } } ] } }