Security researcher Zheng Yu demonstrated database RCE exploits affecting PostgreSQL, MySQL, Oracle, and ClickHouse.
Low-privilege accounts can reach memory-corruption bugs in engine code.
Details cover PostgreSQL CVE-2026-116331, MySQL CVE-2026-101786, and Oracle chaining bugs like CVE-2026-114819, alongside ClickHouse testing.
No exploits have been seen in real attacks yet.
Researcher Zheng Yu from Depthfirst has demonstrated such issues in popular database systems, including PostgreSQL, MySQL, Oracle, and ClickHouse. According to the research, the ability of an account to create temporary objects is enough to cause a problem in the program's memory management, allowing access to the system.
Which systems are affected?
- PostgreSQL: The issue allows a restricted account to execute code with the privileges of the user running the database. The fix was released on November 12 for versions prior to 18.7, 17.12, 16.16, 15.20, and 14.25.
- MySQL: The issue affects Server and Cluster versions 26.7.0 through 26.7.1. The company released an update that fixes the issue on October 20.
- OracleDatabase: Here the attack does not require any account. By combining two different issues (one in Oracle Text and the other in the GraphQL interface), someone could gain access. Fixes for these issues were released on October 20 and November 17.
- ClickHouse: An issue was identified in version 26.7.5.10 when reading data when a specific setting is set to zero. There is no official fix for ClickHouse yet.
What does this mean for administrators?
So far there is no evidence that these problems have been used in real attacks and the above combinations of moves have not been independently tested by other researchers.
However, system administrators should take the following actions:
- Immediately install the updates that manufacturers have released for the systems they use.
- Carefully check account permissions and remove the ability to create temporary tables from all users who do not need it for their work.
>Stay connected with Hacks.gr
Set us as a preferred source on Google and find us on social media.
Preferred source
↗
end of article
Top comments (0)