Automated Threat Modeling

Quick Look: Oracle MySQL Server GIS Flaw CVE-2026-127428 Enables Authenticated DoS and Limited Data Reads

A brief summary of CVE-2026-127428, a CVSS 7.1 flaw in the Oracle MySQL Server: GIS component that lets a low-privileged network user cause a complete denial of service and read a limited subset of data. Includes affected versions and Oracle's November 2026 CSPU patch information.

CVE Analysis

6 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-17

Quick Look: Oracle MySQL Server GIS Flaw CVE-2026-127428 Enables Authenticated DoS and Limited Data Reads

Introduction

A flaw in MySQL's spatial (GIS) subsystem may let any authenticated user who can reach the server over the network, even with a low-privileged account, hang or repeatedly crash it and read a limited slice of data they should not see. Oracle fixed the issue, tracked as CVE-2026-127428, in its November 2026 Critical Security Patch Update. The affected range covers every supported MySQL Server line listed (8.4, 9.7 and 26.10) plus MySQL Cluster releases going back to 8.0.

Oracle rates the vulnerability CVSS 3.1 7.1 (High). That number describes intrinsic severity, not observed attacker activity. As of November 18, 2026, the public reporting we reviewed does not show exploitation in the wild. TheHackerWire reports no confirmed public exploit code, and both TheHackerWire and Rapid7 report that the CVE is not in the CISA Known Exploited Vulnerabilities catalog. Rapid7 lists EPSS as unavailable, and no threat actor or campaign has been tied to this issue.

Technical information

What Oracle disclosed

Oracle's risk matrix places CVE-2026-127428 under MySQL Server, MySQL Cluster, component Server: GIS, with the MySQL Protocol listed as the protocol. The CVE description says the issue is reachable "via multiple protocols", and the risk matrix states it is not remotely exploitable without authentication.

The full vector is:

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H

Broken out:

  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low
  • User Interaction: None
  • Scope: Unchanged
  • Confidentiality: Low
  • Integrity: None
  • Availability: High

This profile describes an authenticated network attack whose largest impact is on availability. It does not describe remote code execution, data modification, or unrestricted database disclosure.

Impact

Oracle lists two distinct outcomes of successful exploitation:

  1. A hang or frequently repeatable crash of MySQL Server or MySQL Cluster, resulting in complete denial of service.
  2. Unauthorized read access to a subset of data accessible to the affected products. Oracle does not say which records or data categories may be exposed.

Both matter for prioritization. Treating this purely as a crash bug understates the confidentiality component that pushes the score to 7.1.

Root cause: what is known and what is not

The GIS subsystem parses geometry data and executes spatial functions on behalf of SQL statements. Beyond naming that component, Oracle has not published the underlying defect, the affected source code, the triggering spatial function, or a sample statement. No upstream commit or diff is public, so there is no vulnerable code to show here.

No confirmed CWE is attached to the CVE record. VulDB lists CWE-404 as an unconfirmed classification, and it should not be treated as an established root cause.

A repeatable crash or hang combined with a limited information disclosure is typical of a memory safety or input validation flaw in geometry handling, which would make stricter validation or bounds checking of geometry data before processing the most likely fix. That is an inference. Oracle has not confirmed the mechanism, and the GIS label on its own does not establish memory corruption, SQL injection, or any other specific weakness class.

Attack flow

The public record does not contain a reproducible exploitation sequence. The disclosed vector and description do support a general outline of an attack:

  1. The attacker holds low-privileged credentials for the target MySQL Server or MySQL Cluster instance. The specific privilege required has not been disclosed.
  2. The attacker reaches the server over the network using the MySQL Protocol. No interaction from another user is needed.
  3. The attacker submits requests that the Server: GIS component processes. The specific function, statement, or geometry input has not been disclosed.
  4. Processing that input causes the server to hang or crash, and the attacker can trigger the condition repeatedly, producing a complete denial of service. The same flaw can also expose a limited subset of accessible data to the attacker.

Because authentication is a prerequisite, exposure is concentrated where many accounts, applications, or tenants can connect to a shared MySQL instance with low privileges.

Patch information

Oracle fixed CVE-2026-127428 in its November 2026 Critical Security Patch Update (CSPU), published November 17, 2026. It is one of 10 new security patches for Oracle MySQL in that CSPU. No upstream commit, diff, or detailed technical write-up has been released. As with most Oracle MySQL issues, the vendor advisory is the main evidence that a fix exists.

Where the fixed builds come from

Oracle directs customers to the MySQL Patch Availability Document, My Oracle Support document CPU440, for fixed builds and installation steps. The advisory itself does not name a fixed version, and the upper bounds of the affected ranges should not be used to infer one.

Fixed release status as of November 18, 2026

  • The latest public releases, 8.4.13 and 9.7.4 (both released 2026/10/20), fall inside the affected range and do not contain the fix.
  • The official release notes indexes list MySQL 8.4.13.1 and MySQL 9.7.4.1 as "Not yet released." These point releases look like the vehicle for the November CSPU fixes on the Community lines, but Oracle has not yet confirmed that they contain the fix for this CVE.
  • Enterprise and Cluster customers should obtain fixed builds through the Patch Availability Document.
  • Community users should check the release notes for 8.4.13.1, 9.7.4.1, and later 26.x releases when they are published to confirm the fix is included.

NVD lookups for this CVE were returning "CVE ID Not Found" at the time of the patch review. That reflects ingestion lag, not a missing patch. Oracle's advisory is the authoritative fix reference.

Interim measures and their limits

Oracle's general advisory guidance allows two temporary risk-reduction measures while patching is pending: blocking network protocols required by an attack, and removing privileges or package access that an attack requires. For this CVE, Oracle has not published a specific blocking rule or the exact privilege involved, so neither measure can be prescribed precisely. Oracle notes both may break application functionality, recommends testing them on nonproduction systems, and states that neither corrects the underlying problem or constitutes a long-term solution.

Affected systems and versions

Oracle lists the following supported releases as affected:

MySQL Server

  • 8.4.0 through 8.4.13
  • 9.7.0 through 9.7.4
  • 26.10

MySQL Cluster

  • 8.0.0 through 8.0.50
  • 8.4.0 through 8.4.13
  • 9.7.0 through 9.7.4
  • 26.10

The Cluster list includes an 8.0 branch that does not appear in the Server list, so check each product against its own range. The absence of MySQL Server 8.0 from this CVE should not be read as a general assurance for older installations. Oracle states that unsupported releases are not tested against the vulnerabilities addressed in the update and that earlier releases may also be affected. CSPU patches are supplied for releases under Premier Support or Extended Support.

Vendor security history

The GIS component has appeared in Oracle's MySQL advisories recently. The July 2026 MySQL Community Edition Security Advisory listed CVE-2026-61108, another Server: GIS issue affecting MySQL Server and MySQL Cluster 9.7.0 through 9.7.1. It shared the network, low-complexity, low-privilege, no-user-interaction profile, with a CVSS score of 6.5 and high availability impact but no confidentiality or integrity impact.

CVE-2026-127428 differs in two material ways: it adds a limited confidentiality impact, raising the score to 7.1, and its affected release coverage is much broader. The public disclosures do not establish a shared root cause, a failed earlier fix, or exploitation of either issue.

More broadly, Oracle operates quarterly Critical Patch Updates, monthly Critical Security Patch Updates for targeted priority fixes, and a Security Alert mechanism for urgent issues, and it reserves the ability to ship fixes outside that schedule. Oracle has also noted that attackers have sometimes succeeded because customers did not apply available patches. That is general ecosystem context and is not evidence that this particular CVE is being exploited.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization