-
Skipping Percona Server for MySQL 8.4.9 and 9.7.0
Upstream MySQL published an out-of-schedule release this week with two high-severity CVE fixes. We’ve pulled those fixes into our next builds and are skipping the two versions we had already queued: Percona Server for MySQL 8.4.9 and 9.7.0.
These fixes arrived through Oracle’s new monthly Critical Security Patch Updates (CSPUs), which Oracle announced begin May 28, 2026. CSPUs ship targeted high-severity fixes between Oracle’s quarterly Critical Patch Updates. For MySQL, these updates are issued as needed rather than on a fixed monthly schedule, so out-of-schedule security fixes like these may become more common.
We’ve handled a skip like this before. When MySQL Community Server 8.4.2 followed 8.4.1 by only a few weeks, we skipped 8.4.1 and shipped its contents in 8.4.2-2. This is the same approach.
What’s happening
The code for 8.4.9 and 9.7.0 was already ready for packaging when the CVE fixes landed. Rather than ship those builds and follow immediately with a security patch, we applied the fixes, re-tested, and re-tagged. Percona Server for MySQL 8.4.10 and 9.7.1 will carry everything 8.4.9 and 9.7.0 would have contained, plus the upstream high-severity CVE fixes.
These fixes come from Oracle’s June 2026 Critical Security Patch Update; the specific CVE identifiers will be listed in the 8.4.10 and 9.7.1 release notes. No action is required on your part. The fixes reach you in 8.4.10 and 9.7.1, expected within days. If your security policy requires faster remediation, contact Percona Support to discuss interim options.
8.4.9 and 9.7.0 will not appear in the package repositories. A normal upgrade moves you straight to 8.4.10 or 9.7.1, which carry the skipped versions’ content.
Who this affects
If you were waiting specifically for 8.4.9 or 9.7.0, those versions won’t be published. Point your upgrade at the next releases instead, which include the same content and the CVE fixes. The delay is a few days, not weeks. If you weren’t tracking a specific version number, nothing changes for you.
What to do
Nothing urgent. Upgrade to the next Percona Server for MySQL releases as you normally would once they’re published. We’ll announce them through release notes and the Percona Blog. For questions about timing or the security content, reach out to Percona Support or post in the Percona Community Forum.
What to expect going forward
Oracle’s monthly CSPUs mean out-of-schedule fixes will happen more often. Our approach stays consistent: we evaluate every upstream release, and when high-severity fixes land between our scheduled releases, we fold them into the next release rather than shipping a separate build for each one. Your LTS support commitments don’t change. We’re watching how often Oracle uses the monthly cadence and will adjust release planning if the volume warrants it.
The post Skipping Percona Server for MySQL 8.4.9 and 9.7.0 appeared first on Percona.
-
Continuing the Conversation: MySQL Community Engagement Across JAPAC
One of the key themes of the MySQL Community over the past year has been increasing transparency, participation, and collaboration. Through Public Discussions, Design Proposals, the MySQL Developer Guide, GitHub collaboration, and the MySQL Contributor Summit, we have been working to create more opportunities for the community to engage with the future direction of MySQL. […]
-
Join MySQL Public Discussion #5: Community Participation, Governance, and Next Steps
As part of our ongoing MySQL Community engagement series, we are pleased to invite you to Public Discussion #5, taking place on July 15, 2026, at 7:00 AM PT. Over the past several months, these public discussions have helped us continue the conversation around MySQL Community Edition, roadmap transparency, contribution paths, GitHub collaboration, and ways […]
-
From JSON by Hand to a Guided MySQL Enterprise Edition Audit Filter Wizard
MySQL Enterprise Edition includes powerful audit filtering capabilities, but writing audit filter JSON by hand can be tedious and error-prone. The JSON model is flexible, which is exactly what makes it useful, but it also means that a small typo, a missing event class, or an incorrectly assigned user can change what does or does […]
-
The Next Phase of MySQL Community Engagement: Accelerating Participation and Collaboration
For over 30 years, MySQL has grown through the contributions, feedback, and collaboration of a global community of developers, database administrators, customers, partners, educators, and open source advocates. That community has helped make MySQL one of the world’s most widely used open source databases. As the ecosystem continues to grow and evolve, so do the opportunities for collaboration. Over the past year, we have […]
|
