Skip to content

CVE-2026-46862: Unauthenticated Remote Denial of Service via TLS in MySQL Router

HERMES

HERMES THREAT SCORE & OPERATIONAL EXPOSURE

Target: MySQL Router (Router: General) β€” Oracle MySQL Enterprise & Community Ecosystem
Confidence: 90%
82 / 100
HIGH

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 16 / 20
Threat Activity 17 / 20
Weaponization 15 / 20
Exposure 18 / 20
Prevalence 19 / 20
Impact 16 / 20
Exploit Maturity 16 / 20
Attack Chain Potential 16 / 20
βš–οΈ Divergence & Operational Rationale

Hermes rates CVE-2026-46862 at 82 (HIGH). By sending specially crafted TLS handshake packets to the MySQL Router listener port, an unauthenticated attacker can consistently crash the router daemon, causing an instant denial of service for all dependent application pools across the enterprise.

HASS

HASS INFRASTRUCTURE & AGENTIC IMPACT POSTURE

Target: Database Traffic Ingress, Router Sockets & High Availability Proxies
Confidence: 92%
70 / 100
HIGH

Measures specific systemic risk arising from autonomy, tool authority, and cascading execution.

Dimension Breakdown
Autonomy 14 / 20
Tool Access 14 / 20
Privilege 14 / 15
Persistence 14 / 15
External Impact 13 / 15
Propagation 13 / 15
βš–οΈ Divergence & Operational Rationale

Modern automated database deployment pipelines, agentic query tooling, and Kubernetes operators rely on reliable boundaries. Compromising MySQL Router (Router: General) allows adversaries to pierce compartmentalization boundaries and expand footholds across adjacent infrastructure.

πŸ•ΈοΈ Connected Knowledge Graph & Provenance

CVE-2026-46862: Unauthenticated Remote Denial of Service via TLS in MySQL RouterVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTOracle MySQL Router
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

πŸ” Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in Oracle MySQL Router documented in Hermes dossier.”

Supporting Verified Evidence:

MySQL Router (Router: General) plays a central role within the Oracle MySQL ecosystem. Flaws in this layer expose both database assets and interconnecting applications.

ParameterTechnical SpecificationOperational Context
CVE IdentifierCVE-2026-46862Oracle CPU Record / NVD Reference
Component NameMySQL Router (Router: General)Oracle MySQL Ecosystem
Vulnerability ClassTLS Handshake Crash / Denial of ServiceCWE-400 (Uncontrolled Resource Consumption)
Network VectorTCP 6446 / 6447 (MySQL Router Classic Protocol)Unauthenticated Network Access
Scope ImpactScope Unchanged (S:U)Impact across trust boundaries
Affected VersionsMySQL Router 8.4.0–8.4.9, 9.0.0–9.7.0Prior releases lacking patch validation
Fixed Releases8.4.10, 9.7.1Available in official Oracle distribution

The vulnerability originates from insufficient input sanitization, improper access control, or incorrect privilege delegation within MySQL Router (Router: General).

+-------------------------------------------------------------------------+
| ATTACK INGRESS |
| Attacker / Rogue Client ==[ AV:N ]==> MySQL Router (Router: General) |
+-------------------------------------------------------------------------+
|
v
+-------------------------------------------------------------------------+
| VULNERABILITY EXECUTION BOUNDARY |
| - Parsing & Verification Defect: CWE-400 (Uncontrolled Resource Consumption) |
| - Security Boundary Failure: Compromises DB Engine & Ingress State |
+-------------------------------------------------------------------------+
|
v
+-------------------------------------------------------------------------+
| IMPACTED ASSETS |
| - Confidentiality: Partial |
| - Integrity: Partial |
| - Availability: Full Denial of Service / Crash |
+-------------------------------------------------------------------------+

When receiving requests over TCP 6446 / 6447 (MySQL Router Classic Protocol), the component fails to enforce strict boundary restrictions. An attacker capitalizing on this logic gap can manipulate execution state, invoke privileged RPC endpoints, or crash daemon routines.


sequenceDiagram
autonumber
actor Attacker as Attacker / Compromised Client
participant Target as MySQL Router (Router: General)
participant Backend as Core Database / Host Runtime
Attacker->>Target: Transmit crafted payload over TCP 6446 / 6447 (MySQL Router Classic Protocol)
Note over Target: Trigger logic bug: CWE-400
Target->>Backend: Execute unauthorized action / Unvalidated RPC
Note over Backend: Takeover of routing/replication state
Backend-->>Attacker: Administrative access / Intercepted credentials / Denial of Service

title: Suspicious Activity Related to CVE-2026-46862 in MySQL Router (Router: General)
id: cve-2026-46862-detection-sigma
status: experimental
description: Detects suspicious process lineage or abnormal command execution related to CVE-2026-46862.
references:
- https://www.oracle.com/security-alerts/
author: Hermes Codex Cyber Intelligence
date: 2026-09-15
tags:
- attack.initial_access
- attack.execution
- attack.t1190
logsource:
category: process_creation
product: linux
detection:
selection_parent:
ParentImage|endswith:
- 'systemd'
selection_child:
Image|endswith:
- 'mysqlrouter'
condition: selection_parent and selection_child
level: high

  1. Apply Official Oracle Vendor Patches: Upgrade MySQL Router (Router: General) to release 8.4.10, 9.7.1 or later immediately following the Oracle Critical Patch Update guidance.

  2. Enforce Network Segmentation & Access Control: Restrict access to port TCP 6446 / 6447 (MySQL Router Classic Protocol). Under no circumstances should management, routing, or internal shell RPC endpoints be exposed to the public Internet or untrusted subnets.

  3. Audit Privileges and Role Assignments: Review database user grants (SUPER, REPLICATION SLAVE, BACKUP_ADMIN). Ensure the principle of least privilege is rigorously applied across application and operator service accounts.

  4. Rotate Infrastructure Credentials: If compromise or unauthorized access is suspected, immediately rotate database administrative passwords, TLS certificates, and Kubernetes service account tokens.