On this page (8 sections)

Ubuntu has published USN-9046-1, a security notice stating that multiple security issues were discovered in MySQL. Updated packages are available for several Ubuntu releases.

If you run MySQL on Ubuntu, whether for a WordPress site, an online store or an internal application, you should plan to apply this update. The notice is short, so this article also covers what it does not say and how to check and update your own servers.

At a glance

What the notice says

The Ubuntu notice is brief. It says multiple security issues were discovered in MySQL and lists how each release was updated:

  • Ubuntu 26.04 LTS: updated to MySQL 8.4.13.
  • Ubuntu 26.10: updated to MySQL 9.7.4.
  • Ubuntu 22.04 LTS and 24.04 LTS: packages updated with backported patches, meaning the fixes were applied to the existing MySQL version rather than moving to a new one.

The notice also warns that the updated packages contain bug fixes, new features and possibly incompatible changes in addition to the security fixes. It points to the MySQL 8.4.13 release notes, the 9.7.4 release notes and the Oracle security alert page for October 2026 for details.

What we do not know yet

The research for this story is a single primary source, the Ubuntu notice itself. It does not list CVE identifiers, CVSS scores, the affected components or the nature of the flaws, and it does not say whether any of them are being exploited. We will not guess at any of that.

Because the notice names Oracle's October 2026 security alert page as a reference, the individual CVE details and severity ratings are likely to be found there and in the MySQL release notes. Read those before deciding how urgent the update is for your environment.

Without severity information, the sensible default is the usual one for database software: apply vendor security updates promptly, after a backup and a short test.

Who is realistically exposed

The notice applies to MySQL packages shipped by Ubuntu. You are in scope if any of these are true:

  • You installed MySQL server or client packages with apt on Ubuntu 22.04 LTS, 24.04 LTS, 26.04 LTS or 26.10.
  • Your web application, CMS or store uses a local MySQL instance on one of those releases.
  • You manage hosting servers or containers built on those Ubuntu releases that include MySQL.

If you run MariaDB, a managed cloud database, or MySQL installed from Oracle's own repositories or a container image, this notice does not directly cover you. Check your own vendor's advisories instead.

How to check your exposure

These read-only commands show which Ubuntu release you run and which MySQL packages are installed. Run them on the server and compare the result with the update you receive.

Show the Ubuntu release (run on the server)Shell
lsb_release -a
List installed MySQL packages and their versions (Debian/Ubuntu); no output means MySQL is not…Shell
dpkg -l | grep -i mysql
Show which MySQL package version apt would install, and which is currently installed (replace…Shell
apt-cache policy mysql-server

On Ubuntu 22.04 LTS and 24.04 LTS the fix is backported, so the upstream version number may not change. Rely on the package version in the Ubuntu notice and package changelog rather than the number MySQL reports about itself.

What to do now

  1. Take a fresh backup of your databases and confirm you can restore it.
  2. Read the Ubuntu notice and the linked MySQL release notes for changes that could affect your setup, since the notice warns of possibly incompatible changes.
  3. If you can, apply the update on a staging copy first and test your application.
  4. Update the MySQL packages on production during a quiet window.
  5. Restart MySQL if the update does not do so, and confirm your application connects and works.
  6. Re-check the package version and review the MySQL error log for startup problems.

This refreshes the package lists and upgrades only the MySQL server package. Run it on Ubuntu after your backup. Look for the new package version in the output.

Upgrade the MySQL server package only (Debian/Ubuntu)Shell
sudo apt update
sudo apt install --only-upgrade mysql-server
Caution. Updating MySQL can restart the database service and briefly interrupt every site or application that depends on it. Schedule a maintenance window, and do not skip the backup, because the notice says the new packages may contain incompatible changes.
Check the service state after the update (systemd)Shell
systemctl status mysql
Tip. If you manage many servers, enable unattended security upgrades so that Ubuntu security notices like this one are applied without waiting for a manual run, and still keep database backups current.

Monitoring after the update

  • Watch your site and application for database connection errors or slow queries in the hours after the restart.
  • Review the MySQL error log and system logs for failed logins or unexpected restarts.
  • Make sure MySQL is not reachable from the public internet unless you truly need it. Limit access to the application servers that use it.
  • Track future Ubuntu and Oracle notices, since a database vendor update cycle brings fixes regularly.

If you also want an outside view of your sites, Webforta Scan runs read-only security scans of websites you verify, and Webforta Monitor watches uptime, certificates and DNS. Neither replaces patching the database server itself.

For wider hardening, see our small business website security guide and the WordPress security checklist if your database backs a WordPress site.

Timeline

Known dates from the research
DateEvent
2026-11-11Ubuntu publishes USN-9046-1 for MySQL

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. USN-9046-1: MySQL vulnerabilitiesubuntu.com ·
  • Ubuntu
  • MySQL
  • USN
  • patching
  • database security