Is there a public exploit for CVE-2026-101513?

No public exploit for CVE-2026-101513 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-101513?

CVE-2026-101513 scores CVSS 3.8 (v3.1), rated low. EPSS puts the chance of exploitation in the next 30 days at 0.17%.

What does CVE-2026-101513 affect?

CVE-2026-101513 affects Oracle Corporation MySQL Cluster.

3.8 Low

Vulnerability in the MySQL Cluster product of Oracle MySQL (component: InnoDB).

CVE-2026-101513

Vulnerability in the MySQL Cluster product of Oracle MySQL (component: InnoDB). Supported versions that are affected are 8.0.0-8.0.37. Difficult to exploit vulnerability allows physical access to compromise MySQL Cluster. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Cluster. CVSS 3.1 Base Score 3.8 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:P/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H).

Assessment

CVSS: 3.8 (v3.1)
Severity: Low
EPSS: 0.17% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 20 October 2026
Last updated: 5 November 2026
Affected: Oracle Corporation · MySQL Cluster
Assigner: oracle

CVSS vectorCVSS:3.1/AV:P/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H

At the source

EUVD (ENISA)

References

https://www.oracle.com/security-alerts/cpuoct2026.html

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 2 + 3? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-101513