LiveActive security incident?Get immediate response
CVE Record

CVE-2022-21526: Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer).

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.29 and prior. 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
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a MySQL Server denial-of-service issue. A highly privileged user who can reach the database over the network may be able to hang or repeatedly crash MySQL, disrupting applications that depend on it. The sources do not indicate data theft, data modification, or active exploitation.

Executive priority

Treat this as a scheduled but real availability risk. It is not currently evidenced as exploited and requires high privileges, but an outage in a critical MySQL-backed application can still create business disruption.

Technical view

CVE-2022-21526 affects Oracle MySQL Server 8.0.29 and prior in the Server: Optimizer component. The CVSS 3.1 score is 4.9 with network access, low complexity, high privileges required, no user interaction, and high availability impact only.

Likely exposure

Exposure is most relevant where MySQL 8.0.29 or earlier is reachable by highly privileged database users or administrative services. Internet exposure alone is less decisive because exploitation requires high privileges, but production databases remain sensitive to availability loss.

Exploitation context

The provided sources and KEV status do not support active exploitation. The attacker must already hold high privileges and have network access through supported MySQL protocols. Successful exploitation is described as a hang or frequently repeatable crash causing complete denial of service.

Researcher notes

The source bundle gives product, component, version range, CVSS vector, and impact, but not detailed root cause or exact fixed version. Avoid assuming broader MySQL forks or products are affected unless vendor advisories confirm them.

Mitigation direction

  • Apply Oracle July 2022 CPU guidance for affected MySQL deployments.
  • Update vendor-packaged MySQL builds, including Fedora packages where applicable.
  • Check NetApp guidance if MySQL is embedded in affected NetApp products.
  • Restrict privileged MySQL access to trusted administrators and management hosts.
  • Monitor database availability and crash events until remediation is complete.

Validation and detection

  • Inventory MySQL Server instances and identify versions 8.0.29 and prior.
  • Confirm whether Oracle, Fedora, or appliance vendor updates have been applied.
  • Review privileged MySQL accounts and remove unnecessary administrative access.
  • Verify network paths to MySQL are limited to approved systems.
  • Check logs and monitoring for unexplained hangs or repeated crashes.
Prepared
Confidence
high
Sources
5

Public sources used

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-2022-21526 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
4Source 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-2022-21526Attack 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 Server8.0.29 and priorListed
Weakness

CWE details

No CWE listed

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