CVE-2026-46862
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 · uneditedVulnerability in the MySQL Router product of Oracle MySQL (component: Router: General). Supported versions that are affected are 8.4.0-8.4.9 and 9.0.0-9.7.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via TLS to compromise MySQL Router. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Router. CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 confidenceAn unauthenticated remote attacker with network access via TLS can exploit MySQL Router versions 8.4.0-8.4.9 and 9.0.0-9.7.0 to cause a complete denial of service. The vulnerability requires no authentication and is easily exploitable, allowing the attacker to send specially crafted packets that cause the router to hang or crash repeatedly.
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>= 8.4.0, <= 8.4.9>= 9.0.0, <= 9.7.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify MySQL Router versionRun 'mysqlrouter --version' or check the installed package version using your system's package manager (e.g., 'rpm -q mysqlrouter' or 'dpkg -l mysql-router')Affected if The version falls within 8.4.0-8.4.9 or 9.0.0-9.7.0
-
Confirm MySQL Router is runningCheck for running mysqlrouter process using 'ps aux | grep mysqlrouter' or check service status via 'systemctl status mysqlrouter'Affected if MySQL Router is actively running and serving connections
-
Verify TLS listener is enabledInspect MySQL Router configuration file (commonly in /etc/mysqlrouter/mysqlrouter.conf or /etc/myrouter.conf) for [tls] section or port bindings indicating TLS is enabledAffected if TLS interface is configured and listening
-
Check for crash or hang indicatorsReview MySQL Router error logs (typically in /var/log/mysqlrouter/ or the configured log directory) for sudden exits, segfaults, or connection spikes around the time of suspected attackAffected if Logs show unexplained crashes, hangs, or repeated restarts
-
Assess network exposureUse 'netstat -tlnp' or 'ss -tlnp' to identify which network interfaces and IP addresses the MySQL Router TLS port is bound to, and verify whether it is exposed to untrusted networksAffected if TLS port is bound to 0.0.0.0 or an externally accessible interface without firewall protection
You are affected if MySQL Router version is between 8.4.0-8.4.9 or 9.0.0-9.7.0 AND the TLS interface is enabled and reachable from the network.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade MySQL Router to version 8.4.10 or later, or 9.7.1 or later. If immediate patching is not feasible, restrict network access to the TLS interface using firewall rules or network segmentation to limit exposure to untrusted networks.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46862 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46862 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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