Skip to content
major vulnerability· requires attention

Affects a widely-used enterprise DB component (MySQL NDB Cluster); remote data access could disrupt data integrity across deployments.

Infrastructure

CVE-2026-46861

9.6
Critical
EPSS 0.36%Patch availableJun 17, 2026

Remote low-priv attacker via HTTP can compromise MySQL NDB Cluster.

common questions

Is CVE-2026-46861 being exploited?

Not confirmed. CVE-2026-46861 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.

How severe is CVE-2026-46861?

CVE-2026-46861 is rated Critical with a CVSS score of 9.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-46861?

Yes. A fix has been recorded for CVE-2026-46861. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-46861 affect?

CVE-2026-46861 affects MySQL NDB Cluster, NDB Operator, Oracle MySQL NDB. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-46861?

Apply vendor patch when released

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
MySQL NDB ClusterNDB OperatorOracle MySQL NDB
impact

Remote attacker can read and modify/delete data across the NDB Cluster, risking data confidentiality and integrity.

action required

Patch when possible

affected versions
Oracle Corporation MySQL NDB Cluster
  • affected>= 8.0.11 and <= 8.0.46
  • affected>= 8.4.0 and <= 8.4.9
  • affected>= 9.0.0 and <= 9.7.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free