PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-101743 Oracle Corporation CVE debrief

A vulnerability in MySQL Server and MySQL Cluster allows a low-privileged attacker with network access to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server and MySQL Cluster. The vulnerability affects MySQL Server versions 26.7.0-26.7.1 and MySQL Cluster versions 26.7.0-26.7.1. This issue is exploitable over multiple protocols, emphasizing the need for defenders to assess exposure and prioritize patching, especially in environments with low-privileged network access.

Vendor
Oracle Corporation
Product
MySQL Server
CVSS
MEDIUM 6.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-20
Original CVE updated
2026-10-28
Advisory published
2026-10-20
Advisory updated
2026-10-28

Who should care

Defenders responsible for MySQL Server and MySQL Cluster installations, especially in environments with low-privileged network access, should assess exposure and prioritize patching.

Why it matters

Defenders should care about CVE-2026-101743 because it allows low-privileged attackers to cause a hang or crash of MySQL Server and MySQL Cluster, potentially impacting availability.

  • Potential for complete DOS of MySQL Server and MySQL Cluster
  • Need for verification of exposure in MySQL Server and MySQL Cluster installations
  • Requirement for patching or mitigating vulnerable versions
  • Potential impact on availability due to CVSS score of 6.5

Technical summary

The vulnerability is in the Server: GIS component of MySQL Server and MySQL Cluster, with a CVSS score of 6.5. It can be exploited over multiple protocols, allowing low-privileged attackers to cause a hang or crash of MySQL Server and MySQL Cluster. Defenders should focus on verifying exposure in installations, especially where low-privileged network access is common, and prioritize patching or mitigating vulnerable versions. The vulnerability's impact on availability is significant, with potential for complete DOS of MySQL Server and MySQL Cluster.

Defensive priority

Defenders should prioritize verifying exposure of MySQL Server and MySQL Cluster installations, especially in environments where low-privileged network access is common.

Recommended defensive actions

  • Verify MySQL Server and MySQL Cluster installations for exposure
  • Assess network access controls to limit low-privileged access
  • Monitor for potential DOS attacks
  • Apply vendor patches when available
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD vulnerability detail page provide information on the vulnerability, its impact, and affected versions. Defenders should verify MySQL Server and MySQL Cluster installations for exposure, focusing on environments with low-privileged network access. Evidence from official sources indicates a CVSS score of 6.5, highlighting the medium severity of this vulnerability.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-101743 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-101743

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-101743 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-101743

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.