PostgreSQL, MySQL, Oracle, ClickHouse: low-privilege SQL accounts reach code execution (CVE-2026-116331)
Severity: critical · Patch status: partial · Since 2026-11-18 · CVE-2026-101786, CVE-2026-114819, CVE-2026-116331, CVE-2026-91609
Depthfirst researcher Zheng Yu published a technical write-up with proofs of concept showing that SQL accounts with very little privilege can reach memory-corruption bugs in the engine code of PostgreSQL, MySQL, ClickHouse and Oracle Database. The clearest vendor-confirmed case is PostgreSQL CVE-2026-116331: an account that can create objects can run code as the database OS user; fixed in 18.7, 17.12, 16.16, 15.20 and 14.25 on 12 November 2026. MySQL CVE-2026-101786 (Server and Cluster 26.7.0 to 26.7.1) is reached, per the researcher, with only temporary-table rights, although Oracle scores it as needing high privileges; the fix shipped in the 20 October 2026 CPU. Oracle Text CVE-2026-114819 (vendor score 9.9, fixed in the 17 November 2026 CPU) needs a Create Session account, and the Oracle REST Data Services GraphQL flaw CVE-2026-91609 (fixed in the 20 October 2026 CPU) needs low privileges over HTTP. The researcher says an exposed GraphQL endpoint lets an unauthenticated attacker chain the two to run commands before login; that pre-auth chain is the researcher's claim and was not reproduced independently. ClickHouse 26.7.5.10 has an integer-overflow write reached when a user sets formatbinarymaxstringsize to 0; it has no CVE and no confirmed fix. No in-the-wild exploitation is reported. Patch PostgreSQL, MySQL, Oracle Database and ORDS, ask ClickHouse for a fix, remove TEMPORARY and temporary-table rights from accounts that do not need them, and keep ORDS GraphQL off untrusted networks.
What to do
- Patch PostgreSQL, MySQL, Oracle Database and Oracle REST Data Services to the fixed versions immediately
- Contact the ClickHouse vendor to confirm a fixed version; restrict or monitor the format_binary_max_string_size setting
- Revoke TEMPORARY privileges and broad temporary-table rights from database accounts that do not need them
- Review what database accounts can do (create objects), not only what they can read
- Ensure Oracle REST Data Services / GraphQL endpoints are not exposed to untrusted networks
Fixed versions
- PostgreSQL 18.7, 17.12, 16.16, 15.20, 14.25 (released 2026-11-12)
- MySQL Server and Cluster: fixed in the Oracle October 2026 CPU (2026-10-20); fixed build number not confirmed from a source I could open
- Oracle Database (Oracle Text, CVE-2026-114819): fixed in the Oracle November 2026 CPU (2026-11-17); fixed release numbers not confirmed
- Oracle REST Data Services (CVE-2026-91609): fixed in the Oracle October 2026 CPU (2026-10-20); the CPU product line reads 24.2.0-26.2.2, so 26.2.2 is likely the fixed release but this is not stated per CVE
- ClickHouse: no confirmed fixed version (researcher reproduced on 26.7.5.10; no CVE)
Sources
All live incidents on Threat Watch