dbcve.org
Mysql ClusterDatabase / datastore · Oracle

CVE-2021-35590

MEDIUM · 6.3 CVSS v3.1 Published 2021-10-20
Fix available
A fix is available. Upgrade to after 8.0.26 or later.
See remediation →
63/100
Remediation priority · Elevated
High EPSS Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the MySQL Cluster product of Oracle MySQL (component: Cluster: General). Supported versions that are affected are 7.4.33 and prior, 7.5.23 and prior, 7.6.19 and prior and 8.0.26 and prior. Difficult to exploit vulnerability allows high privileged attacker with access to the physical communication segment attached to the hardware where the MySQL Cluster executes to compromise MySQL Cluster. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Cluster. CVSS 3.1 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-787

The program writes past the bounds of a buffer, overwriting adjacent memory an attacker can turn to their advantage. Crafted input can overwrite control data and redirect execution. Remediation is validating every index and length before a write, plus modern memory-safety mitigations.

General guidance for the out-of-bounds write class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mysql ClusterDatabase / datastore
Affected:>= 7.4.0, <= 7.4.33>= 7.5.0, <= 7.5.23>= 7.6.0, <= 7.6.19>= 8.0.0, <= 8.0.26
Oncommand InsightApplication
Affected:all versions
SnapcenterApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
High
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 8.0.26
Vendor patch www.oracle.com →
Recommended fix High confidence

MySQL Cluster 7.4.34, 7.5.24, 7.6.20, or 8.0.27 (depending on your current major version line)

  1. 1. Identify the current MySQL Cluster version using: mysql --version or mysqld --version
  2. 2. Based on your current major version line, plan the upgrade path: For 7.4.x, upgrade to 7.4.34 or later; For 7.5.x, upgrade to 7.5.24 or later; For 7.6.x, upgrade to 7.6.20 or later; For 8.0.x, upgrade to 8.0.27 or later
  3. 3. Review Oracle's October 2021 Critical Patch Update for full patch details: https://www.oracle.com/security-alerts/cpuoct2021.html
  4. 4. Perform a complete backup of the MySQL Cluster data directory before upgrading
  5. 5. Test the upgrade in a non-production environment first
  6. 6. During maintenance window, stop MySQL Cluster services on all nodes
  7. 7. Upgrade MySQL Cluster binaries to the fixed version on all nodes
  8. 8. Restart MySQL Cluster services and verify cluster health status
Caveat Upgrading MySQL Cluster across major versions (e.g., 7.x to 8.x) may require schema compatibility checks and could have replication/connection changes; always review MySQL Cluster upgrade documentation before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $2,850. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-35590 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-35590 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data