Skip to main content
CVE-2025-50087VulnerabilityPublished Updated

CVE-2025-50087: Oracle MySQL Cluster · Easily exploitable vulnerability allows high privileged attacker with network access via multiple

Affects Oracle MySQL ClusterSource CVE Database V5

0

Not known to be exploited · CVSS 4.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
4.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-26.

What to do

Affected software

ProductAffectedFixed in
Mavencom.oracle/mysqlpkg:maven/com.oracle/mysqlOther threatsAffected
  • =7.6.0
  • =8.0.0
  • =8.4.0
  • =9.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-50087 effectively, European organizations should: 1) Immediately audit and restrict administrative and high-privilege accounts to minimize the risk of credential compromise or misuse. 2) Implement strict network segmentation and firewall rules to limit network access to MySQL Cluster nodes only to trusted management and application servers. 3) Monitor and log all high-privilege activities within MySQL Cluster environments to detect anomalous behavior indicative of exploitation attempts. 4) Apply the latest security patches from Oracle as soon as they become available; in the absence of patches, consider temporary workarounds such as disabling vulnerable protocols or services if feasible. 5) Conduct regular vulnerability assessments and penetration testing focused on MySQL Cluster configurations and access controls. 6) Employ multi-factor authentication (MFA) for administrative access to reduce the risk of credential-based attacks. 7) Review and harden MySQL Cluster configuration settings to enforce the principle of least privilege and minimize exposed attack surfaces. These targeted actions go beyond generic advice by focusing on access control, network restrictions, and proactive monitoring tailored to the vulnerability's characteristics.

Description

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). 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. 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 creation, deletion or modification access to critical data or all MySQL Server accessible data. CVSS 3.1 Base Score 4.9 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N).

References

Community reviews

Loading reviews…