dbcve.org
Mysql RouterDatabase / datastore · Oracle

CVE-2026-46860

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to after 9.7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the MySQL Router product of Oracle MySQL (component: Router: General). Supported versions that are affected are 9.0.0-9.7.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise MySQL Router. Successful attacks of this vulnerability can result in takeover of MySQL Router. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a critical unauthenticated remote code execution vulnerability in MySQL Router (versions 9.0.0-9.7.0) accessible via HTTP network vector. Successful exploitation grants the attacker complete takeover of the MySQL Router component, potentially allowing pivoting to connected MySQL servers.

MitigationUpgrade MySQL Router to a patched version beyond 9.7.0. If immediate patching is not possible, restrict HTTP interface access to trusted networks only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mysql RouterDatabase / datastore
Affected:>= 9.0.0, <= 9.7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm MySQL Router is installed
    Run 'mysqlrouter --version' to verify the binary exists and retrieve its version number
    Affected if The command returns a version number, indicating MySQL Router is present
  2. Identify the installed version
    Parse the version output from 'mysqlrouter --version' and compare it to the affected range: 9.0.0 through 9.7.0 inclusive
    Affected if The installed version is greater than or equal to 9.0.0 and less than or equal to 9.7.0
  3. Locate the MySQL Router configuration file
    Check common configuration locations such as /etc/mysqlrouter/ or search for .conf files containing 'mysqlrouter' - typical filenames include mysqlrouter.conf or router.conf
    Affected if A MySQL Router configuration file exists on the system
  4. Verify if HTTP server interface is enabled
    Open the configuration file and search for an [http_server] section - check if it exists and contains settings (indicating HTTP is enabled)
    Affected if The configuration contains an [http_server] section with active settings, making the HTTP network vector available
  5. Determine HTTP server network exposure
    In the [http_server] section of the config file, check the 'bind_address' directive - if it is set to 0.0.0.0 or a public IP rather than 127.0.0.1, the interface is externally accessible
    Affected if The HTTP server binds to 0.0.0.0 or a non-localhost address, exposing it to network attack

You are affected if MySQL Router versions 9.0.0-9.7.0 are installed with the HTTP server interface enabled and accessible from untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 9.7.0
Interim mitigation

Upgrade MySQL Router to a patched version beyond 9.7.0. If immediate patching is not possible, restrict HTTP interface access to trusted networks only.

Recommended fix Moderate confidence

MySQL Router 9.7.1 or later (or the latest 9.x release)

  1. 1. Check the current installed version of MySQL Router: mysqlrouter --version
  2. 2. Download the latest MySQL Router version from Oracle's official download page (www.oracle.com) - look for MySQL Router 9.7.1 or later
  3. 3. Stop the MySQL Router service before upgrading
  4. 4. Install the new MySQL Router package using your system's package manager or installer
  5. 5. Verify the new version was installed correctly: mysqlrouter --version
  6. 6. Start the MySQL Router service
  7. 7. Test that MySQL Router is functioning properly and can connect to MySQL servers
Caveat Review Oracle's release notes for any configuration or behavioral changes between your current version and the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mysql Router Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46860 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data