LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21936: Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB).

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.0-8.0.44, 8.4.0-8.4.7 and 9.0.0-9.5.0. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

MediumCVSS 4.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Oracle MySQL vulnerability can let a highly privileged network-accessible attacker crash or hang MySQL Server. The business impact is availability loss, not data theft or alteration based on current sources. Risk is highest where privileged database accounts are broadly available or where MySQL downtime affects critical services.

Executive priority

Treat as a service-availability risk for important MySQL-backed applications. Prioritize systems supporting revenue, operations, or customer-facing services, especially where privileged access is widely delegated. This is not currently evidenced as mass-exploited, but downtime potential justifies timely patch review.

Technical view

CVE-2026-21936 affects Oracle MySQL Server InnoDB in versions 8.0.0-8.0.44, 8.4.0-8.4.7, and 9.0.0-9.5.0. Oracle rates it CVSS 4.9: network exploitable, low complexity, high privileges required, no user interaction, availability impact only. The source bundle also lists Oracle MySQL Cluster affected version families.

Likely exposure

Organizations running affected MySQL Server versions with network-reachable database services and high-privileged users are the likely exposure group. Exposure is reduced when administrative database access is tightly limited and monitored.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked as CISA KEV. Exploitation requires high privileges and network access via multiple protocols, limiting broad opportunistic risk but still relevant for insider, compromised-admin, or lateral-movement scenarios.

Researcher notes

Current public details are limited to Oracle’s advisory/CVE data. The issue is in the InnoDB component and produces complete denial of service through hang or repeatable crash. No CWE, exploit details, or named workaround are provided in the source bundle.

Mitigation direction

  • Review Oracle’s January 2026 Critical Patch Update guidance for this CVE.
  • Upgrade or patch affected MySQL deployments according to Oracle’s advisory.
  • Restrict high-privileged MySQL accounts to necessary administrators and services.
  • Limit network access to MySQL from trusted hosts and application tiers.
  • Increase monitoring for unexpected MySQL hangs, crashes, or repeated restarts.

Validation and detection

  • Inventory Oracle MySQL Server and MySQL Cluster deployments.
  • Compare versions against 8.0.0-8.0.44, 8.4.0-8.4.7, and 9.0.0-9.5.0.
  • Identify systems exposing MySQL over network-accessible protocols.
  • Review which accounts have high privileges on affected instances.
  • Confirm remediation status against Oracle’s January 2026 advisory.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-21936 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H1.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.9Medium
CVSS 3.1 vector shape for CVE-2026-21936Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Oracle CorporationMySQL Cluster7.6.0, 8.0.0, 8.4.0, 9.0.0Listed
Oracle CorporationMySQL Server8.0.0, 8.4.0, 9.0.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.