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-101810 Overview
CVE-2026-101810 is a denial of service vulnerability in Oracle MySQL Router version 26.7.0. The flaw sits in the Router: General component and allows an unauthenticated remote attacker to crash or hang the Router process. Exploitation requires only network access over one of the protocols the Router exposes, with no user interaction. Oracle disclosed the issue in the October 2026 Critical Patch Update. The weakness is classified as improper access control [CWE-284].
Critical Impact
An unauthenticated attacker can trigger a complete denial of service against MySQL Router, severing database connectivity for every downstream application that routes through the affected instance.
Affected Products
- Oracle MySQL Router 26.7.0
Discovery Timeline
- 2026-10-20 - CVE-2026-101810 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-101810
Vulnerability Analysis
MySQL Router is a lightweight middleware component that routes application traffic to backend MySQL InnoDB Cluster or ReplicaSet nodes. The vulnerability resides in the Router: General component and manifests when the Router processes attacker-supplied input over its network-facing protocols. Successful exploitation drives the Router into either a persistent hang or a repeatable crash, producing a complete denial of service.
Because the Router typically fronts database traffic for application tiers, taking it offline interrupts every client that depends on it for connection routing, failover, and load balancing. The vulnerability does not expose confidential data or allow modification of stored records. Availability is the sole impact dimension.
Root Cause
Oracle categorizes the weakness under CWE-284: Improper Access Control. The Router accepts and acts on network input from unauthenticated sources without enforcing sufficient restrictions, which permits an attacker to drive the service into a terminal state. Oracle has not published a code-level breakdown. See the Oracle Security Alert October 2026 for vendor details.
Attack Vector
The attack originates from the network and targets any protocol endpoint the Router exposes to clients. The attacker needs no credentials, no prior session, and no interaction from a legitimate user. Any system that can reach the Router's listener ports, including compromised hosts inside the application tier, can issue the triggering traffic. Because MySQL Router listeners are commonly reachable from application subnets, exposure is broad in typical deployments.
No public proof-of-concept exploit is available at this time, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. The EPSS score is 0.441%.
Detection Methods for CVE-2026-101810
Indicators of Compromise
- Unexpected restarts, crash dumps, or watchdog relaunches of the mysqlrouter process.
- Sudden spikes in connection failures reported by applications downstream of the Router.
- Repeated short-lived TCP connections from unfamiliar sources to Router listener ports (default 6446, 6447, 64460, 64470).
- Router log entries showing abrupt termination without a clean shutdown sequence.
Detection Strategies
- Correlate mysqlrouter process exits with inbound connection patterns to identify the triggering source.
- Alert on repeated Router restarts within a short interval, which signal a repeatable crash condition rather than operational churn.
- Baseline normal client source addresses against the Router and flag new or anomalous originators probing the listener ports.
Monitoring Recommendations
- Forward MySQL Router logs and host process telemetry to a centralized analytics platform for correlation with network flow data.
- Monitor availability metrics (connection success rate, routing latency) and page on sustained degradation.
- Track network reachability of Router ports from untrusted segments and alert on any new exposure path.
How to Mitigate CVE-2026-101810
Immediate Actions Required
- Apply the fixes from the Oracle October 2026 Critical Patch Update to every MySQL Router 26.7.0 instance.
- Restrict network access to Router listener ports so only authorized application hosts can reach them.
- Inventory all MySQL Router deployments, including containerized sidecars and InnoDB Cluster bootstrap installs, to confirm patch coverage.
- Review Router process supervision so a crash-loop is detected and surfaced rather than silently masked by automatic restarts.
Patch Information
Oracle addressed CVE-2026-101810 in the October 2026 Critical Patch Update. Refer to the Oracle Security Alert October 2026 for the fixed Router build and upgrade guidance. Customers running MySQL Router 26.7.0 should upgrade to the version listed in that advisory.
Workarounds
- Place MySQL Router behind firewall rules or security groups that permit traffic only from known application subnets.
- Terminate client traffic at an authenticated proxy or service mesh node that filters malformed protocol input before it reaches the Router.
- Deploy redundant Router instances across isolated network paths so a crash on one instance does not sever all database connectivity.
- Rate-limit new connections to Router listener ports to blunt rapid repeat-crash attempts.
# Example: restrict MySQL Router listener ports to an application subnet
# (adjust interface, subnet, and ports to match your deployment)
iptables -A INPUT -p tcp -s 10.20.0.0/16 --dport 6446 -j ACCEPT
iptables -A INPUT -p tcp -s 10.20.0.0/16 --dport 6447 -j ACCEPT
iptables -A INPUT -p tcp --dport 6446 -j DROP
iptables -A INPUT -p tcp --dport 6447 -j DROP
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

