Skip to main content

MySQL Router CVE-2026-101783

| EUVDEUVD-2026-106184 HIGH
Improper Access Control (CWE-284)
2026-10-20 secalert_us@oracle.com GHSA-w24j-3385-4gmj
7.4
CVSS 3.1 · Vendor: oracle
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach MySQL Router HTTPS endpoint
  2. Delivery
    Send crafted HTTPS requests
  3. Exploit
    Satisfy difficult exploitation conditions
  4. Execution
    Gain unauthorized read/modify access
  5. Impact
    Exfiltrate or alter critical data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK

1 technique across 1 tactic: Defense Evasion

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation targets the HTTPS network interface of Oracle MySQL Router version 26.7.0 (component Router: General). No authentication is required (PR:N) and no user interaction is needed (UI:N), so any attacker with network access to the Router's HTTPS service can attempt it. The primary limiting factor is high attack complexity (AC:H): Oracle explicitly rates it 'difficult to exploit,' indicating the attacker must meet specific, likely non-default or state-dependent conditions (timing, internal state, or configuration) that are outside their direct control, rather than sending a single deterministic request. Impact is confined to confidentiality and integrity of MySQL Router-accessible data; there is no availability/DoS impact (A:N) and no stated scope change (S:U).

Impact

This is a genuinely serious but not top-priority flaw based on the combined signals. The CVSS 3.1 base score of 7.4 (High) reflects a network-reachable (AV:N), unauthenticated (PR:N) vector with high confidentiality and integrity impact (C:H/I:H), but the high attack complexity (AC:H) is the dominant limiting factor - Oracle explicitly labels it 'difficult to exploit,' meaning successful attacks likely require specific conditions, timing, or state the attacker cannot fully control. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no evidence of active or imminent widespread exploitation; exploitation status is 'no public exploit identified at time of analysis.' There is a signal conflict worth noting: the input Tags include 'Authentication Bypass,' yet the description characterizes the attacker as merely 'unauthenticated' (consistent with PR:N) and does not actually describe bypassing an authentication control - treat the auth-bypass characterization as unverified against the primary description. Availability impact is None (A:N), so this is a data confidentiality/integrity concern, not a denial-of-service risk. Net assessment: prioritize patching in MySQL Router 26.7.0 deployments given the unauthenticated network vector and high C/I impact, but the AC:H rating and absence of exploitation evidence place it below actively-exploited or trivially-exploitable issues.

Exploit ScenarioDerived

A remote, unauthenticated attacker with network reachability to a MySQL Router 26.7.0 instance's HTTPS interface crafts and sends specially-tailored requests that, under the right conditions, let them read or alter data accessible to the Router. Because Oracle rates the flaw as difficult to exploit (AC:H), the attacker likely must satisfy non-trivial preconditions or win a race/state condition rather than fire a single reliable request. No public exploit code was identified in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 21, 2026

Oracle MySQL Router 26.7.0 exposes an HTTPS-facing weakness (component Router: General) that can be attacked without credentials (PR:N, UI:N), letting a network-positioned adversary read and tamper with data the Router can reach - scored CVSS 7.4 with High confidentiality and integrity impact but no availability impact. Oracle characterizes exploitation as 'difficult' (AC:H), meaning success depends on timing, internal state, or non-default configuration rather than a single deterministic request, which tempers real-world risk despite the high impact rating. No public exploit code and no CISA KEV entry were identified at time of analysis, and no vendor fix version is documented in the available data beyond the October 2026 Oracle CPU reference.

RemediationAI

No vendor-released patch version is identified in the available data; the only vendor reference is the October 2026 Oracle CPU (https://www.oracle.com/security-alerts/cpuoct2026.html), so confirm the fixed Router build for 26.7.0 there and upgrade as soon as Oracle publishes it - treat the CPU as the authoritative source rather than assuming a version number. Until a patched build is confirmed, apply compensating controls on the HTTPS attack surface: restrict the Router's HTTPS listener with network ACLs/firewall rules so only known management hosts and monitoring systems can reach it (trade-off: breaks remote admin tooling and health checks from unlisted sources), or bind the HTTPS interface to a loopback/management-only address (trade-off: eliminates remote access entirely). Where the REST/HTTPS interface is not operationally required, disable it - this removes the vulnerable attack path outright but forfeits Router's REST-based metadata and configuration features. Front the listener with a reverse proxy or mTLS-terminating gateway that enforces client authentication, since the flaw is reachable without credentials (PR:N) and an added auth layer may block the bypass path (trade-off: added latency and certificate lifecycle management). Monitor Router HTTPS access logs for anomalous or out-of-pattern requests from unexpected sources, and note that exploitation is rated difficult (AC:H), so targeted rather than opportunistic attempts are more likely. Combine with the upstream MySQL server-side patches from the same CPU cycle to avoid leaving adjacent components exposed.

Affected VersionsENISA

MySQL Router 26.7.0

Affected Packages

euvd mysql_router no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

MySQL Router is the lightweight middleware that sits between client applications and InnoDB Cluster / ReplicaSet backends, handling connection routing, read/write splitting, and metadata caching; it exposes an HTTPS administrative/REST interface in addition to its MySQL protocol ports. The flaw lies in the Router: General component reachable over that HTTPS interface and is an authentication/authorization-handling defect (tagged Authentication Bypass by the reporter), which is consistent with the CVSS vector's PR:N - no credentials are needed - combined with C:H/I:H impact: an attacker who can reach the HTTPS listener may be able to bypass or subvert the intended access checks and then create, delete, or modify Router-accessible data and read it in full. The high attack complexity (AC:H) and unchanged scope (S:U) indicate the bypass is conditional - likely dependent on specific internal state, request ordering, or configuration rather than a trivially replayable request - and that the impact remains confined to the Router's own security context rather than escalating to the host OS. No CWE was assigned in the available data, so the precise root-cause class (improper authentication vs. missing authorization check) cannot be confirmed from the provided input.

Know when MySQL gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (oracle) PRIMARY 7.4 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI 7.4 HIGH

Unauthenticated network HTTPS access (AV:N/PR:N/UI:N) with high C/I impact; AC:H because Oracle rates it difficult to exploit; A:N as no availability impact is described.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (oracle).

CVSS VectorVendor: oracle

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

DescriptionCVE.org

Vulnerability in the MySQL Router product of Oracle MySQL (component: Router: General). The supported version that is affected is 26.7.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTPS to compromise MySQL Router. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL Router accessible data as well as unauthorized access to critical data or complete access to all MySQL Router accessible data. CVSS 3.1 Base Score 7.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N).

Executive ViewAI

Why It Matters

Oracle MySQL Router 26.7.0 carries a high-severity HTTPS-facing flaw that lets an unauthenticated network-positioned attacker read and alter data the Router can reach, with high confidentiality and integrity impact and no availability impact. Although exploitation is assessed as difficult (AC:H) and no public exploit was identified at time of analysis, the lack of a vendor-released patch means leadership should treat exposed Router instances as a data-integrity and confidentiality risk until mitigations or a fix are in place.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; restrict HTTPS exposure to trusted networks, segment MySQL Router from sensitive database backends, disable unnecessary HTTPS listeners and non-default configurations, enforce least-privilege network access, and monitor Router and database logs for anomalous read or tamper activity.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Medium
MySQL Router deployed mainly in InnoDB Cluster/routing setups, not every MySQL install
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

37
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +37
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

More in MySQL

View all
CVE-2016-6662 CRITICAL POC
9.8 Sep 20

Oracle MySQL through 5.5.52, 5.6.x through 5.6.33, and 5.7.x through 5.7.15; MariaDB before 5.5.51, 10.0.x before 10.0.2

CVE-2012-5613 MEDIUM POC
6.0 Dec 03

MySQL 5.5.19 and possibly other versions, and MariaDB 5.5.28a and possibly other versions, when configured to assign the

CVE-2017-3599 HIGH POC
7.5 Apr 24

Vulnerability in the MySQL Server component of Oracle MySQL (subcomponent: Server: Pluggable Auth). Rated high severity

CVE-2012-2122 MEDIUM POC
5.1 Jun 26

sql/password.c in Oracle MySQL 5.1.x before 5.1.63, 5.5.x before 5.5.24, and 5.6.x before 5.6.6, and MariaDB 5.1.x befor

CVE-2020-5398 HIGH
7.5 Jan 17

In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16,

CVE-2012-5612 MEDIUM POC
6.5 Dec 03

Heap-based buffer overflow in Oracle MySQL 5.5.19 and other versions through 5.5.28, and MariaDB 5.5.28a and possibly ot

CVE-2012-5611 MEDIUM POC
6.5 Dec 03

Stack-based buffer overflow in the acl_get function in Oracle MySQL 5.5.19 and other versions through 5.5.28, and 5.1.53

CVE-2020-1967 HIGH POC
7.5 Apr 21

Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due

CVE-2016-6664 HIGH POC
7.0 Dec 13

mysqld_safe in Oracle MySQL through 5.5.51, 5.6.x through 5.6.32, and 5.7.x through 5.7.14; MariaDB; Percona Server befo

CVE-2015-3152 MEDIUM POC
5.9 May 16

Oracle MySQL before 5.7.3, Oracle MySQL Connector/C (aka libmysqlclient) before 6.1.3, and MariaDB before 5.5.44 use the

CVE-2026-24479 CRITICAL POC
9.8 Jan 27

HUSTOJ online judge has a path traversal vulnerability enabling arbitrary file access on the competition server.

CVE-2016-2105 HIGH
7.5 May 05

Integer overflow in the EVP_EncodeUpdate function in crypto/evp/encode.c in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy