Skip to main content
Vulnerability Database/CVE-2026-101785

CVE-2026-101785: MySQL Server Auth Bypass Vulnerability

CVE-2026-101785 is an authentication bypass vulnerability in MySQL Server and MySQL Cluster that allows low-privileged attackers to compromise database integrity and availability. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-101785 Overview

CVE-2026-101785 is a high-severity vulnerability affecting the JSON component of Oracle MySQL Server and MySQL Cluster. The flaw allows a low-privileged attacker with network access to compromise database integrity and availability through multiple protocols. Successful exploitation grants unauthorized create, delete, or modify access to all accessible data, read access to a subset of data, and the ability to crash or hang the database for a complete denial of service. The weakness is categorized under CWE-284: Improper Access Control.

Critical Impact

Authenticated network attackers can modify or destroy all accessible MySQL data and trigger a complete database outage.

Affected Products

  • MySQL Server versions 8.4.0 through 8.4.12, 9.7.0 through 9.7.3, and 26.7.0 through 26.7.1
  • MySQL Cluster versions 8.0.0 through 8.0.49, 8.4.0 through 8.4.12, and 9.7.0 through 9.7.3
  • MySQL Cluster versions 26.7.0 through 26.7.1

Discovery Timeline

  • 2026-10-20 - CVE-2026-101785 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-101785

Vulnerability Analysis

The vulnerability resides in the JSON subsystem of the MySQL Server engine, which is shared by MySQL Cluster deployments. An authenticated attacker with limited privileges can send crafted requests over supported network protocols to trigger the flaw. Exploitation does not require user interaction and operates within the vulnerable component's security scope.

The impact profile is unusual. Integrity and availability impacts are high, while confidentiality impact is limited to a subset of data. This indicates the primary damage path is data tampering and process termination rather than wholesale data exfiltration.

Root Cause

The underlying weakness maps to CWE-284: Improper Access Control. The JSON component fails to enforce authorization boundaries properly when processing certain inputs, allowing privilege-constrained users to perform operations outside their intended rights. The Oracle advisory confirms the component as Server: JSON but does not publish deeper internals.

Attack Vector

The attack originates from the network and requires only low privileges. An attacker with any authenticated session to the MySQL instance can issue the malicious request. Multiple protocols are listed as viable delivery channels, which widens the exposure of internet-reachable or multi-tenant database deployments.

No verified public exploit code is available for CVE-2026-101785 at the time of publication. Technical details are limited to the Oracle Critical Patch Update - October 2026.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-101785

Indicators of Compromise

  • Unexpected CREATE, UPDATE, or DELETE operations originating from low-privileged accounts, particularly against tables containing JSON columns
  • Abnormal MySQL process termination or repeated mysqld crashes with core dumps referencing JSON parsing routines
  • Spikes in failed queries or connection resets following JSON-heavy workloads from a single authenticated source

Detection Strategies

  • Enable the MySQL general query log or audit plugin and monitor for anomalous JSON function usage (JSON_EXTRACT, JSON_TABLE, JSON_SET) from accounts without historical JSON activity
  • Correlate authenticated session activity with sudden server restarts in SIEM telemetry to identify DoS attempts
  • Baseline query patterns per database user and alert on deviations involving JSON manipulation functions

Monitoring Recommendations

  • Forward MySQL audit logs and error.log to a centralized data lake for retention and correlation
  • Alert on repeated mysqld process crashes within short intervals from identical source IPs
  • Track privilege use by low-privileged accounts to detect lateral movement into JSON-related operations

How to Mitigate CVE-2026-101785

Immediate Actions Required

  • Apply the fixes referenced in the Oracle Critical Patch Update - October 2026 to all affected MySQL Server and MySQL Cluster instances
  • Inventory all MySQL Server and Cluster deployments and prioritize patching for internet-exposed or multi-tenant databases
  • Audit MySQL user accounts and revoke unnecessary low-privilege accounts that could serve as attack entry points

Patch Information

Oracle addressed CVE-2026-101785 in the October 2026 Critical Patch Update. Administrators should upgrade MySQL Server beyond versions 8.4.12, 9.7.3, and 26.7.1, and MySQL Cluster beyond 8.0.49, 8.4.12, 9.7.3, and 26.7.1. Review the Oracle advisory for the specific fixed build numbers that apply to your platform.

Workarounds

  • Restrict network access to MySQL ports using firewall rules, security groups, or VPC isolation so only trusted application tiers can connect
  • Enforce least-privilege account policies and remove GRANT statements that allow JSON manipulation on sensitive schemas by non-essential accounts
  • Deploy a database activity monitoring layer to filter or alert on suspicious JSON function calls until patching completes
bash
# Configuration example: restrict MySQL network exposure and review privileges
# Limit bind address to internal interface
sed -i 's/^bind-address.*/bind-address = 10.0.0.5/' /etc/mysql/mysql.conf.d/mysqld.cnf
systemctl restart mysql

# Audit accounts with broad privileges
mysql -e "SELECT user, host FROM mysql.user WHERE Super_priv='Y' OR Create_priv='Y';"

# Revoke unnecessary privileges on JSON-heavy schemas
mysql -e "REVOKE INSERT, UPDATE, DELETE ON sensitive_db.* FROM 'reporting_user'@'%';"
mysql -e "FLUSH PRIVILEGES;"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.