What happened
Zheng Yu of Depthfirst published proof-of-concept exploits showing that low-privilege database accounts, even ones that cannot read a single application table, can run code on the database server. The accounts reach memory-corruption bugs in the C/C++ engine code behind ordinary SQL. The researcher argues SQL permissions do not cover that code. No in-the-wild exploitation has been reported, and the full chains were not independently reproduced.
Affected products
| Product | Identifier | Affected | Fixed | Access needed |
|---|---|---|---|---|
| PostgreSQL | CVE-2026-116331 | Before 18.7, 17.12, 16.16, 15.20, 14.25 | Nov 12 | An account that can create objects (default TEMPORARY privilege). Type confusion reached via the temporary schema. |
| MySQL Server and Cluster | CVE-2026-101786 | 26.7.0 to 26.7.1 | Oct 20 | Query optimizer flaw. Oracle rates it as needing high privileges, but the researcher ran code on 26.7.0 with only temp-table creation rights. |
| Oracle Database (Oracle Text) | CVE-2026-114819 (rated 9.9) | 19.3-19.32, 21.3-21.24, 23.4.0-23.26.3 | Nov 17 | None when chained with the REST Data Services flaw. Not rated exploitable without login on its own. |
| Oracle REST Data Services | CVE-2026-91609 | 24.2.0 to 26.2.1 | Oct 20 | GraphQL interface flaw, chained against an exposed web endpoint. |
| ClickHouse | No CVE | 26.7.5.10 (tested) | No confirmed fix | A user who can set format_binary_max_string_size; setting it to zero triggers an integer-overflow write. |
Why it matters
Many teams treat a limited database account as a safe boundary. These exploits show that the ability to create temporary objects or tweak a session setting can be enough to reach engine bugs. Shared and multi-tenant database servers, and applications where SQL injection yields a restricted account, are the most exposed.
Recommended actions
- Install the vendor updates listed above, including the Nov 12 PostgreSQL and Nov 17 Oracle releases.
- Ask the ClickHouse vendor about a fix, and limit who can change settings.
- Review what accounts can do, not just what they can read.
- Remove the TEMPORARY privilege and broad temporary-table rights from accounts that do not need them.
- Do not expose Oracle REST Data Services to untrusted networks. Removing TEMPORARY does not close the Oracle path, which needs no account.
Related
PostgreSQL's November release is covered in PostgreSQL Patches 52 Flaws.
