Oracle's October 2026 advisory lists the MySQL protocol, network access, high privileges and a CVSS 3.1 score of 7.2. Security researcher Zheng Yu describes an out-of-bounds write in windowed bitwise aggregation and reports a working code-execution chain.Those privilege descriptions need to stay separate. Oracle's risk matrix rates the flaw as requiring high privileges, while the researcher's tested chain used an account granted only CREATE TEMPORARY TABLES. That test does not establish that every deployment is reachable from the same limited role.
What it allows
How Does CVE-2026-101786 Reach MySQL Memory?
According to Zheng Yu's research, the affected windowed bitwise aggregate sizes a counter array when a prepared statement is prepared. At execution, a longer bound value can make the aggregate update counters beyond that allocation. The resulting out-of-bounds writes affect session memory and can corrupt nearby internal state.
The researcher says their proof of concept used ordinary session features to shape that memory and redirect cleanup behavior. They report command execution under the MySQL service account on the official 26.7.0 image. Their tested account had CREATE TEMPORARY TABLES permission but no SELECT access to existing application tables.
Oracle's advisory does not describe this chain. It marks remote exploitation without authentication as unavailable and assigns high required privileges. The distinction matters for vulnerability prioritization: do not treat the published limited-role test as an unauthenticated attack.
Our defensive reading is to review which application and tenant roles can connect to affected servers and create temporary tables. Access logs, database audit records and service-account process telemetry may help investigate unusual activity, but these are general triage steps rather than a published detection signature. Use the Vulnerability Intelligence platform to organize exposure review against Oracle's affected-version list.
Who is affected
Which Releases Are Affected by CVE-2026-101786?
Oracle lists MySQL Server 26.7.0 through 26.7.1 and MySQL Cluster 26.7.0 through 26.7.1 as the supported affected ranges for this CVE. The row does not list the 8.0, 8.4 or 9.7 branches for this particular flaw. Record the exact running release and installation package for each server and Cluster node.
The advisory labels these as affected versions, not fixed releases. It directs administrators to the corresponding MySQL release documentation for the release containing the fix. The public 26.7 release notes reviewed for this draft list 26.7.0 and 26.7.1, so this profile does not assert an unverified fixed-version threshold.
Use Oracle's October security update and release documentation to choose the applicable patched build or package. The patch management process should record the installed package and confirm the running release after deployment. Where a package carries a backported fix, verify its security bulletin rather than judging it only by a version string.
Timeline
- 2026-10-20
Oracle published its October MySQL Community Edition advisory, listing CVE-2026-101786 and affected releases.
- 2026-11-18
Zheng Yu published technical research and described a code-execution proof of concept against MySQL 26.7.0.
What to do
-
Inventory affected MySQL installations
Identify MySQL Server and MySQL Cluster 26.7.0 or 26.7.1 installations. Record the running version, package source and owners of every server and Cluster node.
-
Apply the applicable Oracle security update
Use Oracle's October 2026 advisory and corresponding release documentation to select the supported patched build or package. Follow your distribution's security bulletin if it backports the fix.
-
Verify the deployed fix
After updating, confirm the running release and installed package or patch identifier on every affected node. Compare each result with the applicable vendor or distribution security documentation.
-
Review temporary-table grants
Check which roles can connect to affected servers and create temporary tables. Restrict grants that applications and tenants do not need while the update is deployed.
-
Investigate suspicious activity
Review available database audit records and service-account process telemetry for unusual activity around affected sessions. Treat findings as investigation leads, not a CVE-specific detection signature.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-101786 in Brandefense Atlas
The Atlas record of CVE-2026-101786: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Can a user with only temporary-table privileges exploit CVE-2026-101786?
Zheng Yu reports a proof of concept on MySQL 26.7.0 using CREATE TEMPORARY TABLES and no SELECT access to existing application tables. Oracle's matrix still lists high privileges.
Does CVE-2026-101786 affect MySQL 8.4?
Oracle's row names only MySQL Server and MySQL Cluster 26.7.0 through 26.7.1 for this CVE. Check other October advisory rows separately for flaws affecting 8.4.
Is there evidence of attacks against deployed servers?
The research describes a working proof of concept. That is distinct from evidence of attacks against deployed servers, and the available primary material does not establish such a campaign.
How should administrators verify a fix?
Use Oracle's October update documentation for the installed branch, then compare the running release and package or patch identifier on each affected node.
Sources
- MySQL Community Edition Security Advisory: October 2026Oracle MySQL
- Narrow Grants, Wide EnginesZheng Yu, Depthfirst
- CVE-2026-101786 RecordNVD
- MySQL 26.7 Release NotesOracle MySQL