LiveActive security incident?Get immediate response
CVE Record

CVE-2021-35625: Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges).

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges). 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 read access to a subset of MySQL Server accessible data. CVSS 3.1 Base Score 2.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N).

LowCVSS 2.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2021-35625 is a low-severity MySQL Server privileges issue. An attacker already holding high privileges and network access could read some data they should not access. The business risk is mainly confidentiality exposure in databases still running MySQL Server 8.0.26 or earlier.

Executive priority

Treat this as scheduled remediation, not an emergency, unless sensitive databases still run affected versions with broad privileged access. Prioritize patching alongside other Oracle CPU database updates and privilege-reduction work.

Technical view

Oracle describes this as a MySQL Server Security: Privileges vulnerability affecting supported versions 8.0.26 and prior. It is network-accessible, low-complexity, requires high privileges, needs no user interaction, and has limited confidentiality impact only. CVSS 3.1 score is 2.7.

Likely exposure

Exposure is most likely in MySQL Server deployments at version 8.0.26 or earlier, especially where privileged database accounts can connect over network-accessible protocols. The provided sources do not identify additional affected products beyond Oracle MySQL Server.

Exploitation context

The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. Exploitation requires a high-privileged attacker with network access, which materially limits urgency compared with unauthenticated or low-privilege database flaws.

Researcher notes

The main constraint is privilege level: CVSS PR:H means validation should focus on version exposure, privilege boundaries, and whether high-privilege accounts can reach the server remotely. The sources do not provide exploit details, exploit-in-the-wild evidence, or a named standalone workaround.

Mitigation direction

  • Follow Oracle Critical Patch Update guidance for affected MySQL Server deployments.
  • Upgrade MySQL Server 8.0.26 and earlier systems per vendor guidance.
  • Restrict MySQL network access to trusted hosts and applications.
  • Review and reduce high-privilege database accounts where possible.
  • Monitor database access logs for unusual privileged read activity.

Validation and detection

  • Inventory MySQL Server instances and record exact versions.
  • Confirm whether any instance runs 8.0.26 or earlier.
  • Review firewall and bind-address exposure for MySQL services.
  • Audit high-privilege MySQL accounts and network access paths.
  • Check vendor advisories for product-specific remediation status.
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-35625 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
Low
CVSS
2.7 (3.1)
Known Exploited
No
Published

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

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
2.7CVSS 3.1LowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N1.21.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.7Low
CVSS 3.1 vector shape for CVE-2021-35625Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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.