dbcve.org
Mysql Ndb ClusterDatabase / datastore · Oracle

CVE-2026-46861

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to after 9.7.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 NDB Cluster product of Oracle MySQL (component: Cluster: NDB Operator). Supported versions that are affected are 8.0.11-8.0.46, 8.4.0-8.4.9 and 9.0.0-9.7.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise MySQL NDB Cluster. While the vulnerability is in MySQL NDB Cluster, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL NDB Cluster accessible data as well as unauthorized access to critical data or complete access to all MySQL NDB Cluster accessible data. CVSS 3.1 Base Score 9.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N).

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 · moderate confidence

Vulnerability in the MySQL NDB Cluster NDB Operator component allows a low-privileged attacker with network access via HTTP to modify or access critical data. The NDB Operator manages MySQL NDB Cluster deployments in Kubernetes and the vulnerability enables unauthorized data modification or complete access to NDB Cluster data, with scope expansion to impact additional products.

MitigationApply Oracle's published patches for affected versions (8.0.11-8.0.46, 8.4.0-8.4.9, 9.0.0-9.7.0). Until patched, restrict network access to the NDB Operator's HTTP interface and implement additional authentication layers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 Ndb ClusterDatabase / datastore
Affected:>= 8.0.11, <= 8.0.46>= 8.4.0, <= 8.4.9>= 9.0.0, <= 9.7.0

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm NDB Operator deployment
    Check for NDB Operator pods or deployments in Kubernetes: `kubectl get deployments,statefulsets -A | grep -i ndb` or `kubectl get pods -A | grep -i ndb-operator`
    Affected if NDB Operator is present in the environment and the version falls within the affected ranges below
  2. Identify MySQL NDB Cluster version
    Retrieve the MySQL NDB Cluster version from the NDB pods or operator-managed resources: `kubectl get pods -n <ndb-namespace> -o jsonpath='{.items[*].spec.containers[*].image}'` and look for mysql cluster images
    Affected if The installed NDB Cluster version is 8.0.11 through 8.0.46, 8.4.0 through 8.4.9, or 9.0.0 through 9.7.0
  3. Verify NDB Operator API network exposure
    Check if the NDB Operator service is exposed externally: `kubectl get svc -A` and inspect service type, ports (typically 8081, 8443 for operator APIs), and any Ingress/LoadBalancer configurations
    Affected if The NDB Operator API service is accessible via HTTP/HTTPS from untrusted networks or the public internet
  4. Audit NDB Operator access controls
    Review RBAC policies and user access to the NDB Operator: `kubectl auth can-i get ndbclusters --as=<user>` for sample low-privilege users, and examine ClusterRoleBindings/RoleBindings related to NDB operator resources
    Affected if Low-privileged users or service accounts have read/write/delete permissions on NDB Cluster resources via the operator API

You are affected if NDB Operator is deployed with a MySQL NDB Cluster version within 8.0.11-8.0.46, 8.4.0-8.4.9, or 9.0.0-9.7.0 and the operator API is network-accessible to low-privilege users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 9.7.0
Interim mitigation

Apply Oracle's published patches for affected versions (8.0.11-8.0.46, 8.4.0-8.4.9, 9.0.0-9.7.0). Until patched, restrict network access to the NDB Operator's HTTP interface and implement additional authentication layers.

Fix this in Mysql Ndb Cluster Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46861 — 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-2026-46861 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