OSSeva Blog
SecurityMySQL vulnerabilities by version: Oracle's 2026 advisories for 8.0, 8.4 and 9.7
MySQL vulnerabilities in 2026: how many, and in which versions
Oracle's four 2026 Critical Patch Updates carry 206 new security patches for Oracle MySQL, 161 of them for MySQL Server, and 20 of those Server patches carry an Oracle CVSS score of 7.0 or higher. The numbers come from the MySQL risk matrix in each Oracle advisory, read on 17 November 2026, and each Server CVE was checked as published on the CVE Program API. MySQL 8.0 appears in the January and April advisories and in neither the July nor the October one, because it reached end of life on 30 April 2026.
The window. The complete counts and per-CVE checks here cover the four 2026 advisories (January, April, July and October). The four 2025 advisories are summarised by Oracle's own headline totals only, because they were not re-checked CVE by CVE. Oracle lists supported versions only, so a version missing from an advisory has not been shown to be safe; it has not been assessed.
Running MySQL in production? OSSeva patches and supports it, end-of-life versions included.
MySQL extended support: what is coveredHow many security patches does Oracle ship for MySQL each quarter?
Oracle ships MySQL fixes four times a year, in its January, April, July and October Critical Patch Updates, and the October 2026 advisory was the largest of the eight read: 98 new patches. The 2025 rows show Oracle's headline totals; the 2026 rows are split by product from the text-form risk matrix.
| Advisory | New MySQL patches (all products) | MySQL Server | Server rated 7.0 or higher | Lines listed for MySQL Server |
|---|---|---|---|---|
| January 2025 | 39 | Not recounted | Not recounted | 8.0, 8.4, 9.x Innovation |
| April 2025 | 43 | Not recounted | Not recounted | 8.0, 8.4, 9.x Innovation |
| July 2025 | 40 | Not recounted | Not recounted | 8.0, 8.4, 9.x Innovation |
| October 2025 | 18 | Not recounted | Not recounted | 8.0, 8.4, 9.x Innovation |
| January 2026 | 20 | 13 | 2 | 8.0, 8.4, 9.x Innovation |
| April 2026 | 34 | 27 | 1 | 8.0, 8.4, 9.x Innovation |
| July 2026 | 54 | 41 | 4 | 8.4, 9.7 |
| October 2026 | 98 | 80 | 13 | 8.4, 9.7, Innovation 26.7 |
Sources: the Oracle Critical Patch Update advisories for January, April, July and October 2025 and 2026 at oracle.com/security-alerts, with the MySQL risk matrix counted from each advisory's text form, read on 17 November 2026. "New MySQL patches" is Oracle's own headline figure and includes MySQL Cluster, Connectors, Router, Workbench, Shell and Enterprise Backup rows. A patch is one row of the risk matrix, and a few CVEs appear on more than one row.
Which MySQL versions does each advisory list?
MySQL 8.4 is listed in every one of the eight advisories, 8.0 in the first six, 9.7 in the last two and 5.7 in none. Oracle's advisories name the supported versions that are affected, so the lines table is also a map of who still gets fixes.
| MySQL line | Oracle support status | Advisories listing it for MySQL Server (of 8, January 2025 to October 2026) | Last advisory listing it |
|---|---|---|---|
| 5.7 | Ended 31 October 2023 | 0 | None in the window |
| 8.0 | Ended 30 April 2026; final release 8.0.46 on 21 April 2026 | 6 | April 2026 (8.0.0 to 8.0.45) |
| 8.4 LTS | Premier Support to April 2029, Extended to April 2032 | 8 | October 2026 (8.4.0 to 8.4.12) |
| 9.7 LTS | Generally available 21 April 2026; Premier Support to April 2031 | 2 | October 2026 (9.7.0 to 9.7.3) |
| Innovation (9.0 to 9.6, 26.7) | Supported until the next Innovation release | Listed while supported | October 2026 (26.7.0 to 26.7.1) |
Support dates are from Oracle's Lifetime Support Policy as read for MySQL 8.0 EOL on 15 November 2026; release dates are from the MySQL release notes, which date 8.0.46 to 21 April 2026, 8.4.13 and 9.7.4 to 20 October 2026. The October advisory lists 8.4 up to 8.4.12 and 9.7 up to 9.7.3 as affected, so those are the builds it covers.
Which MySQL vulnerabilities in 2026 were rated 7.0 or higher?
20 MySQL Server patches in the 2026 advisories carry an Oracle CVSS 3.1 base score of 7.0 or higher, and 4 of them score 9.0 or above. The 20 patches cover 19 distinct CVEs, because CVE-2025-15467 is patched in both the April and the October advisory. Five of the 20 are third-party components Oracle bundles (OpenSSL, curl and SQLite), and the score shown is Oracle's rating, which can differ from the component maintainer's own rating. Every ID below is published on the CVE Program API.
| Advisory | CVE | Oracle CVSS | Component | MySQL versions Oracle lists as affected |
|---|---|---|---|---|
| Jan 2026 | CVE-2025-6965 | 9.8 | Docker Images (SQLite) | 8.4.0-8.4.7 |
| Jan 2026 | CVE-2025-9230 | 7.5 | Packaging (OpenSSL) | 8.0.0-8.0.44, 8.4.0-8.4.7, 9.0.0-9.5.0 |
| Apr 2026 | CVE-2025-15467 | 9.8 | Packaging (OpenSSL) | 8.0.0-8.0.45, 8.4.0-8.4.8, 9.0.0-9.6.0 |
| Jul 2026 | CVE-2026-60163 | 8.4 | Group Replication Plugin | 8.4.0-8.4.10, 9.7.0-9.7.1 |
| Jul 2026 | CVE-2026-60315 | 8.2 | X Plugin | 8.4.0-8.4.10, 9.7.0-9.7.1 |
| Jul 2026 | CVE-2026-60316 | 7.2 | X Plugin | 8.4.0-8.4.10, 9.7.0-9.7.1 |
| Jul 2026 | CVE-2026-61094 | 7.2 | Replication | 8.4.0-8.4.10, 9.7.0-9.7.1 |
| Oct 2026 | CVE-2025-15467 | 9.8 | Compiling (OpenSSL) | 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1 |
| Oct 2026 | CVE-2026-9547 | 9.8 | Compiling (curl) | 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1 |
| Oct 2026 | CVE-2026-101781 | 8.8 | Group Replication GCS | 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1 |
| Oct 2026 | CVE-2026-101785 | 8.3 | JSON | 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1 |
| Oct 2026 | CVE-2026-101770 | 8.1 | Client programs | 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1 |
| Oct 2026 | CVE-2026-101771 | 8.1 | Client programs | 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1 |
| Oct 2026 | CVE-2026-101772 | 8.1 | Client programs | 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1 |
| Oct 2026 | CVE-2026-101679 | 7.5 | Client programs | 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1 |
| Oct 2026 | CVE-2026-101796 | 7.5 | Replication | 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1 |
| Oct 2026 | CVE-2026-101797 | 7.5 | mysqldump | 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1 |
| Oct 2026 | CVE-2026-101775 | 7.4 | Replication | 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1 |
| Oct 2026 | CVE-2026-101786 | 7.2 | Optimizer | 26.7.0-26.7.1 |
| Oct 2026 | CVE-2026-101773 | 7.1 | Group Replication Plugin | 8.4.0-8.4.12, 9.7.0-9.7.3, 26.7.0-26.7.1 |
CVE-2025-6965 (SQLite), CVE-2025-9230 and CVE-2025-15467 (OpenSSL) and CVE-2026-9547 (curl) are third-party CVEs that Oracle patched inside MySQL packages. The other 15 distinct CVEs were assigned by Oracle. Third-party records are in the CVE Program as published by their own maintainers, so their scores in the API may differ from Oracle's.
Does MySQL 8.0 get security fixes after end of life?
Not from Oracle: the July and October 2026 advisories carry 121 MySQL Server patches between them and list 8.0 in none. Seventeen of the 121 are rated 7.0 or higher, two of them 9.8. Because Oracle's advisory names supported versions only, the advisory does not say whether 8.0.46 is affected by each one; it says no 8.0 build contains the fix.
That gap grows by one advisory every quarter. For servers that stay on 8.0, the sources of fixes are a provider's own extended support programme on managed services (Amazon RDS Extended Support from 1 August 2026), or patched 8.0 Community builds backported by a third party. OSSeva ships signed 8.0 Community builds with security fixes backported, with Critical CVEs patched within 48 hours and High within 7 days. The decision tree, the 8.4 upgrade path and the PostgreSQL option are on the MySQL 8.0 EOL page, and the full cost-and-options view is MySQL extended support.
Which MySQL version should you run to be covered by the October 2026 advisory?
Run 8.4.13 or later on the 8.4 LTS series, or 9.7.4 or later on 9.7. Oracle's October 2026 advisory lists affected versions up to 8.4.12 and 9.7.3, and the release notes date 8.4.13 and 9.7.4 to 20 October 2026, the date the CVE records carry. An 8.0 server cannot go straight to 9.7: MySQL does not allow skipping an LTS series, so 8.0 goes to 8.4 first. The MySQL 8.0 to 8.4 upgrade guide lists the breaking changes to test.
How to check a MySQL server against the advisories
Compare the exact version string with the affected range in the advisory row, not just the series. The steps:
- Run
SELECT VERSION();on each server, and list the MySQL Router, Shell and client builds separately, since they have their own rows. - Find the advisory for each quarter since the release of your build, and read the MySQL Server rows whose affected range includes your version.
- Note third-party rows (OpenSSL, curl, SQLite): they can apply to a package or Docker image rather than the server code.
- Move to the lowest release that is outside every affected range, or record the CVE and the compensating control for any server that cannot move.
Sources and method
Oracle Critical Patch Update advisories and their verbose (risk matrix) pages for January, April, July and October 2025 and 2026, read on 17 November 2026. The MySQL Server rows were parsed from the text form of the risk matrix, and the parsed row counts for 2026 match the headline figure Oracle prints on each advisory (20, 34, 54 and 98). All 163 Server CVE IDs in the 2026 advisories and in the 2025 rows rated 7.0 or higher were checked on the CVE Program API (cveawg.mitre.org) and are published. The advisory sections for MySQL Cluster, Connectors, Router, Workbench, Shell and Enterprise Backup are counted in the all-products column and are not analysed here. The July 2025 advisory's text form lists one more row than the 40 patches Oracle states, which is why 2025 Server counts are not shown.
Frequently asked questions
How many vulnerabilities does MySQL have?
Oracle's four 2026 Critical Patch Updates carry 206 new security patches for Oracle MySQL, of which 161 are for MySQL Server. The four 2025 advisories carry 140 by Oracle's headline totals (39, 43, 40 and 18).
Which MySQL versions are affected by the October 2026 vulnerabilities?
Oracle lists MySQL Server 8.4.0 to 8.4.12, 9.7.0 to 9.7.3 and Innovation 26.7.0 to 26.7.1 as affected, with some rows limited to 26.7. MySQL 8.0 is not listed because it is no longer supported.
Is MySQL 8.0 vulnerable?
8.0.46 has received no fix for the 121 Server patches in Oracle's July and October 2026 advisories. Oracle does not say which of them affect 8.0, because its advisories cover supported versions only. See MySQL 8.0 EOL.
Is MySQL 5.7 still getting security fixes?
No. 5.7 reached end of life on 31 October 2023 and does not appear in any of the eight advisories read.
What is the most serious MySQL vulnerability of 2026?
By Oracle's score, CVE-2025-6965, CVE-2025-15467 and CVE-2026-9547, at 9.8 each. All three are in third-party components bundled with MySQL (SQLite, OpenSSL and curl).
Tags
Related articles
November 2026 Patch Tuesday: the last .NET 8 and .NET 9 updates
November 11, 2026SecurityApache Storm Vulnerabilities by Version: CVEs for Storm 1.2, 2.x and 3.x
October 6, 2026Securityetcd Vulnerabilities by Version: CVEs for etcd 3.3, 3.4, 3.5, 3.6 and 3.7
October 6, 2026SecurityClickHouse Vulnerabilities by Version: CVEs for ClickHouse 22.x to 26.x, LTS and Stable
October 6, 2026SecurityActiveMQ Classic Vulnerabilities by Version: CVEs for 5.15 to 5.19 and 6.x
October 5, 2026SecurityRedis Vulnerabilities by Version: CVEs for Redis 6.2, 7.0, 7.2, 7.4 and 8.x
October 5, 2026Get a quote
Ready to get your open source under control?
Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.
Prefer to talk or read more first?