Low-Privilege Database Accounts Can Be Turned Into Server Takeover, Researcher Shows
A researcher has shown that database accounts with very little access can still be used to run code on the server itself. Zheng Yu of Depthfirst published proof-of-concept exploits against PostgreSQL, MySQL and ClickHouse, plus a separate Oracle chain that needs no login. None has been seen in a real attack, and the full chains were not independently reproduced.
The core argument is that SQL permissions control which tables an account can reach, but not the memory-unsafe C and C++ code the engine uses to read, plan and run a query. Common grants give an account enough room to reach that code. PostgreSQL's default TEMPORARY privilege, or the right to create temporary tables in MySQL and ClickHouse, lets an account create objects or send input that triggers a memory bug.
In PostgreSQL, CVE-2026-116331 lets an account that can create database objects run code as the operating system user running the database. It was fixed last week. MySQL has a similar query optimizer flaw, CVE-2026-101786, in Server and Cluster versions 26.7.0 to 26.7.1. Oracle rates it as needing high privileges, yet the researcher reached code execution with an account that could only create temporary tables. ClickHouse is affected by an integer-overflow write, reproduced on version 26.7.5.10, which has no CVE and no confirmed fixed version.
Oracle Database is the only case needing no account. A bug in Oracle Text (CVE-2026-114819, rated 9.9) and a flaw in the GraphQL interface of Oracle REST Data Services (CVE-2026-91609), chained against an exposed web endpoint, can run commands before any login. Oracle patched them in its November and October updates respectively.
Why it matters
Many teams treat a low-privilege database account as low risk because it cannot read application data, but this research breaks that assumption: the permission model does not protect the engine code beneath it. Anyone running a database where applications or users hold TEMPORARY or temporary-table rights is exposed, and the Oracle path means internet-exposed REST endpoints matter even with no account. Oracle's own rating of the MySQL flaw as needing high privileges understates the access actually required, so severity scores alone should not set patch priority.
What to do
- Install the PostgreSQL fix for CVE-2026-116331 released in the latest security advisory.
- Update MySQL Server and Cluster from versions 26.7.0 to 26.7.1 to a patched release covering CVE-2026-101786.
- Apply Oracle's October and November updates for CVE-2026-91609 and CVE-2026-114819, and check whether Oracle REST Data Services endpoints are exposed.
- Revoke the TEMPORARY privilege and broad temporary-table rights from accounts that do not need them, and ask ClickHouse's vendor about a fix.