LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35631: Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: GIS).

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: GIS). Supported versions that are affected are 8.0.26 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

CVE-2021-35631 can let a highly privileged attacker crash or hang MySQL Server, causing database downtime. It affects Oracle MySQL Server 8.0.26 and prior in the GIS component. The issue is availability-only in the provided sources, with no stated data theft or tampering impact.

Executive priority

Treat this as a service availability risk, not a confirmed breach indicator. Prioritize internet- or broadly network-reachable MySQL servers and systems supporting critical business services, especially where privileged database accounts are widely used.

Technical view

Oracle describes a network-exploitable MySQL Server GIS flaw requiring high privileges and no user interaction. CVSS is 4.9, vector AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H. Successful exploitation can cause a complete denial of service through hangs or repeatable crashes.

Likely exposure

Exposure is most relevant where MySQL Server 8.0.26 or earlier is reachable by users or services holding high database privileges. NetApp published an advisory, so environments using NetApp products should review that advisory for product-specific exposure.

Exploitation context

The provided bundle does not show active exploitation, and the CVE is not marked KEV. Abuse requires network access and high privileges, which reduces broad opportunistic risk but leaves insider, compromised-admin, or over-privileged service-account scenarios relevant.

Researcher notes

Evidence is limited to Oracle, CVE, and NetApp references. The root cause, exploit technique, and exact fixed release are not provided in the bundle. Avoid assuming exploit availability or affected downstream products beyond vendor advisories.

Mitigation direction

  • Review Oracle's October 2021 CPU guidance for MySQL Server remediation.
  • Upgrade affected MySQL Server deployments according to current vendor guidance.
  • Restrict network access to MySQL Server to trusted systems only.
  • Reduce and monitor high-privileged MySQL accounts.
  • Review NetApp advisory if using NetApp products or bundled MySQL components.

Validation and detection

  • Inventory MySQL Server versions and flag 8.0.26 or earlier.
  • Identify systems exposing MySQL over network-accessible protocols.
  • Review privileged MySQL accounts and service account usage.
  • Check monitoring for unexplained MySQL hangs, crashes, or restarts.
  • Confirm Oracle or NetApp remediation guidance has been applied.
Prepared
Confidence
high
Sources
4

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-2021-35631 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
3Source 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-2021-35631Attack 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.26 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.