MySQL Router EUVD-2026-106211

Requires network reachability to a listening MySQL Router instance running version 26.7.0; the description states exploitation is via 'multiple protocols,' so any of Router's exposed listener ports (classic MySQL protocol and/or X Protocol routing endpoints) is a viable entry point. No authentication is required (PR:N) and no user interaction is needed (UI:N), so default network-exposed deployments are vulnerable. The main limiting factors are network exposure (Routers restricted to trusted application subnets or firewalled from untrusted networks are far harder to reach) and the impact ceiling: this is availability-only (A:H, C:N/I:N), so the sole realistic consequence is service disruption of the routing tier, not data compromise.

This is a genuine but bounded availability risk. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) is internally consistent with the description: a remote, unauthenticated attacker over the network with low complexity can trigger a hang or repeatable crash (complete DoS) of MySQL Router, with no confidentiality or integrity impact. The 7.5 score is driven entirely by availability. However, several exploitation signals are absent: no EPSS score is provided, the vulnerability is not listed in CISA KEV, and no public exploit (POC) is referenced - so there is no public exploit identified at time of analysis. The practical ceiling on impact is also important: this is availability-only, so it cannot be used for data theft, code execution, or lateral movement by itself - it degrades or interrupts database connection routing. Net assessment: a real patch-worthy issue for availability-sensitive deployments (MySQL Router sits in the data path of InnoDB Cluster/HA topologies, so a crash can sever application-to-database connectivity), but NOT an urgent emergency absent evidence of active exploitation. Prioritize behind any concurrent confidentiality/integrity or actively-exploited flaws from the same Oracle CPU.

An attacker with network reachability to a MySQL Router instance sends crafted traffic over one of the protocols Router listens on, triggering a logic or parsing fault that hangs or repeatedly crashes the process. Because no authentication or user interaction is required and complexity is low, the attacker can repeat the crash to sustain a denial of service, cutting applications off from the backend MySQL cluster. No public exploit code is referenced at time of analysis.