Data tampering and crash via undisclosed flaw
Published Aug 18, 2026 · Updated Aug 20, 2026
Improper access control in Oracle MySQL Cluster NDB Operator allows remote attackers to modify some data and crash the service via network requests. Oracle has not published the vulnerable code path or patch details, so the mechanism is known only as an undisclosed NDB Operator access-control failure that accepts unauthenticated network requests and permits unauthorized update, insert, or delete operations plus hang or repeatable crash conditions. Exposure is limited to deployments that make the NDB Operator reachable over the relevant MySQL protocols; available records bound the impact to integrity and availability, with no disclosed confidentiality loss or authoritative public exploitation evidence.
Summary
What happened
Improper access control in Oracle MySQL Cluster NDB Operator allows remote attackers to modify some data and crash the service via network requests. Oracle has not published the vulnerable code path or patch details, so the mechanism is known only as an undisclosed NDB Operator access-control failure that accepts unauthenticated network requests and permits unauthorized update, insert, or delete operations plus hang or repeatable crash conditions. Exposure is limited to deployments that make the NDB Operator reachable over the relevant MySQL protocols; available records bound the impact to integrity and availability, with no disclosed confidentiality loss or authoritative public exploitation evidence.
The record
- CVE
- CVE-2026-60592
- Published
- Aug 18, 2026
- Updated
- Aug 20, 2026
- Vendor
- Oracle Corporation
- Product
- MySQL Cluster
- Classifications
- CWE-284
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=8.0.0 <=8.0.47
- Affected versionversion=8.4.0 <=8.4.10
- Affected versionversion=9.7.0 <=9.7.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo