CVE-2025-50081: Oracle MySQL Cluster · Difficult to exploit vulnerability allows high privileged attacker with network access via multiple
Affects Oracle MySQL ClusterSource CVE Database V5
Not known to be exploited · CVSS 3.1 Low.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 15 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Oracle Corporation MySQL Cluster | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Restrict high-privilege access to MySQL Client environments strictly on a need-to-know basis and enforce the principle of least privilege to minimize the number of users who could exploit this vulnerability. 2) Educate and train users with elevated privileges on social engineering risks and the importance of cautious interaction with network requests or prompts that could trigger the vulnerability. 3) Monitor and audit MySQL Client usage, especially mysqldump operations, to detect unusual or unauthorized data access or modification attempts. 4) Implement network segmentation and firewall rules to limit network access to MySQL Clients only from trusted and authenticated sources, reducing the attack surface. 6) Employ multi-factor authentication (MFA) for administrative access to MySQL environments to add an additional layer of security against unauthorized access. 7) Use database activity monitoring tools to detect anomalous queries or data manipulation patterns that could indicate exploitation attempts.
Description
Vulnerability in the MySQL Client product of Oracle MySQL (component: Client: mysqldump). Supported versions that are affected are 8.0.0-8.0.42, 8.4.0-8.4.5 and 9.0.0-9.3.0. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Client. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Client accessible data as well as unauthorized read access to a subset of MySQL Client accessible data. CVSS 3.1 Base Score 3.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N).