RDS MySQL 5.7 Extended Support Extended Through 2029 — Investigating the Contents of the Patch Provided in June 2026

RDS MySQL 5.7 Extended Support Extended Through 2029 — Investigating the Contents of the Patch Provided in June 2026

RDS MySQL 5.7 Extended Support now runs through June 2029. We checked all 14 CVEs in the Year 3 security patch 5.7.44-RDS.20260521 against NVD and Oracle CPU and summarized what the maintenance covers.
2026.06.18

This page has been translated by machine translation. View original

Introduction

On June 17, 2026, AWS announced that it would extend Extended Support for RDS MySQL 5.7 to June 30, 2029. The previous end date was February 28, 2027, so this is an extension of about two and a half years. The Year 3 pricing ($0.200/vCPU-hr) remains unchanged.

https://aws.amazon.com/about-aws/whats-new/2026/06/rds-mysql-es-extension/

Prior to this extension announcement, on June 4, the security patch 5.7.44-RDS.20260521 for after entering Year 3 was released. It includes 14 CVE fixes and 1 bug fix, confirming that Extended Support maintenance is actually functioning in practice. All of the CVEs are DoS-type (CVSS 4.9 to 6.5), and the bug fix addresses a memory leak at shutdown.

https://aws.amazon.com/about-aws/whats-new/2026/06/amazon-rds-mysql-extended-support-minor-5744-rds/

To understand what fixes are actually being provided, I checked all 14 CVEs in the NVD and the Oracle CPU April 2026.

Note that this article is a survey based on public information, and I have not reproduced the vulnerabilities or verified patch application on actual systems.

Summary of Extended Support Additional Charges

The Extended Support additional charges for RDS MySQL 5.7 are as follows (US East (Ohio) region).

Period Date range Additional charge (per vCPU-hr)
Year 1-2 2024/3/1 〜 2026/2/28 $0.100
Year 3 2026/3/1 〜 2029/6/30 $0.200

Monthly Estimate of Extended Support Additional Charges Only

This is an estimate for Single-AZ, 1 instance, converted at 730 hours/month.

Instance class vCPU Year 1-2 Year 3
db.t3.micro 2 $146/month $292/month
db.r5.large 2 $146/month $292/month
db.r5.2xlarge 8 $584/month $1,168/month

Because the Extended Support additional charge is calculated based on the number of vCPUs, the amount is the same for the same vCPU count regardless of the instance class's regular price. This is why db.t3.micro and db.r5.large cost the same.

Also, Reserved Instance discounts do not apply to Extended Support charges.

CVE Survey Results

List of All 14

For all 14 CVEs, I checked the CVSS v3.1 vectors in the NVD and organized the component classification by referring to the Oracle CPU April 2026.

CVE ID Component CVSS v3.1 PR Vector
CVE-2026-34270 Group Replication Plugin 6.5 L CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVE-2026-34271 Group Replication Plugin 6.5 L CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVE-2026-34272 Optimizer 6.5 L CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVE-2026-22004 InnoDB 4.9 H CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CVE-2026-34304 InnoDB 4.9 H CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CVE-2026-35236 InnoDB 4.9 H CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CVE-2026-35237 InnoDB 4.9 H CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CVE-2026-35238 InnoDB 4.9 H CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CVE-2026-21998 Optimizer 4.9 H CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CVE-2026-22002 Optimizer 4.9 H CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CVE-2026-22005 Optimizer 4.9 H CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CVE-2026-34267 Optimizer 4.9 H CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CVE-2026-34278 Optimizer 4.9 H CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
CVE-2026-35240 Optimizer 4.9 H CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

All of these CVEs were disclosed in the Oracle Critical Patch Update April 2026.

Common Characteristics

The characteristics of the CVSS vectors common to all 14 are as follows.

  • Confidentiality (C): None — No direct impact on data leakage is assessed in CVSS
  • Integrity (I): None — No direct impact on data tampering is assessed in CVSS
  • Availability (A): High — May cause the server to hang or crash repeatedly (a complete DoS)

According to public information, all of them are assessed as DoS-type vulnerabilities.

Distribution by Severity

CVSS v3.1 Base Score Required privileges Count
6.5 (MEDIUM) PR:L (authenticated, low privileges) 3
4.9 (MEDIUM) PR:H (high privileges) 11

PR:L (low privileges) assumes a user with DB connection privileges, and PR:H (high privileges) assumes DBA-equivalent privileges.

Breakdown by Component

Component Count
Server: Optimizer 7
InnoDB 5
Server: Group Replication Plugin 2

Optimizer and InnoDB together account for 12 of the total, making up the large majority.

Two Group Replication-related CVEs are included. However, since users do not directly use Group Replication in a normal RDS for MySQL configuration, the practical impact on RDS users is considered low.

About the Three CVSS 6.5 CVEs

The three with relatively higher scores among the 14 are said to be exploitable with authenticated low privileges (PR:L).

  • CVE-2026-34270, CVE-2026-34271 (Group Replication Plugin): May cause a DoS in Group Replication processing. However, as mentioned above, the impact is low in a normal RDS configuration
  • CVE-2026-34272 (Optimizer): May cause a DoS in query optimization processing. This is a path that a low-privileged DB user could reach through normal query execution, and it carries the highest practical risk of the three

In environments where low-privileged DB users are issued widely, it is worth taking the impact of CVE-2026-34272 in particular into consideration.

Summary of Patch Application

All 14 are DoS-type (C:N/I:N/A:H), and the risk of data leakage or tampering is not assessed in public information, so you can decide on applying the patch based on your availability requirements.

Note that CVSS AV:N (Attack Vector: Network) is an assessment meaning "reachable over the network"; it does not mean it can be attacked unauthenticated from the internet. In RDS, actual reachability depends on the configuration such as the VPC, Security Groups, and Public accessibility.

It is worth considering early application in the following environments.

  • Systems with high availability requirements (DoS has a sufficiently serious impact)
  • Environments where low-privileged DB users are issued widely (there are 3 PR:L CVEs)

The actual timing of application should be decided together with the maintenance window, restart impact, and application compatibility checks.

Conclusion

The 14 CVE fixes included in this 5.7.44-RDS.20260521 are all assessed in CVSS as DoS-type (C:N/I:N/A:H). Please consider applying them according to your availability requirements and DB user privilege design. Although the support period has been extended to 2029, we recommend upgrading to MySQL 8.0 or 8.4 LTS at an appropriate time.

Share this article

AWSのお困り事はクラスメソッドへ