The Library

Database RCE: PostgreSQL CVE-2026-116331, ClickHouse, MySQL and Oracle Flaws Show Locked-Down Database Accounts Can Still Reach the Server, and the Fixed Versions

Depthfirst researcher Zheng Yu showed that tight database permissions still leave room for attacks that run code on the server. PostgreSQL CVE-2026-116331 is fixed in 18.7, 17.12, 16.16, 15.20 and 14.25. The ClickHouse fix is in 26.9.1.702.

Elite Performance Exclusive LLC 7 min read

Where Worldwide

Database RCE: PostgreSQL CVE-2026-116331, ClickHouse, MySQL and Oracle Flaws Show Locked-Down Database Accounts Can Still Reach the Server, and the Fixed Versions
On this page 8 sections

A researcher has published working attacks showing that limited access to a database can be turned into code running on the database server itself. PostgreSQL and ClickHouse have confirmed fixes, and related flaws are listed for MySQL and Oracle. If your website, app or back-office system keeps its data in one of these engines, that matters: the database server holds your most valuable data, and a version update is the main fix.

What happened in the database RCE research

The work is by Zheng Yu, a researcher at Depthfirst. The write-up was published on Nov 18, 2026. Its main point, in the researchers' own words: "Restrictive SQL grants leave a surprisingly broad native attack surface intact".

In plain English: many teams protect a database by giving each application account only the permissions it needs. That is still good practice. The research argues it is not enough on its own. Even a tightly scoped account can still reach parts of the SQL engine itself, and bugs in the engine can be used to break out of the database and run commands on the machine. The write-up puts it like this: "a short output from SHOW GRANTS does not mean a small native attack surface".

RCE stands for remote code execution: an attacker gets the server to run commands of their choosing.

What is confirmed, engine by engine

PostgreSQL CVE-2026-116331

This is the best-documented part, because the PostgreSQL project published its own advisory. It describes a type confusion bug in PostgreSQL's min/max aggregate optimization. An account that can create objects in the database can define a custom aggregate with a SORTOP option that makes the query planner treat the aggregate's input and result as the same type when they are not. The advisory says the result is arbitrary code running as the operating system user that runs the database.

  • Severity: CVSS 3.0 overall score 8.8
  • Affected: versions before PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25
  • Fixed: 18.7, 17.12, 16.16, 15.20 and 14.25, each on its own branch

The attacker needs an account that can create objects. Check which of your accounts can do that.

MySQL CVE-2026-101786

MySQL's community security advisory page lists CVE-2026-101786. Our sources confirm the identifier and nothing more: not the affected versions, not a severity score and not the fixed release. Do not assume your version is safe. Open the advisory and compare it with the version you run.

Oracle Database: Oracle Text and Oracle REST Data Services

Two Oracle identifiers are involved. The details below come from third-party vulnerability trackers, not from an Oracle bulletin we confirmed.

  • CVE-2026-114819 is described as a "Vulnerability in the Oracle Text component of Oracle Database Server." The tracker adds: "Successful attacks of this vulnerability can result in takeover of Oracle Text."
  • CVE-2026-91609 is in the GraphQL component of Oracle REST Data Services (ORDS). Supported versions 24.2.0 through 26.2.1 are listed as affected, and successful attacks "can result in unauthorized access to critical data".

The Depthfirst write-up describes an Oracle chain of two vulnerabilities. In its words: "Together, the two vulnerabilities allow an unauthenticated attacker with access only to the exposed HTTP endpoint". That is the worrying part. The attack starts with no database login at all, only network access to the web endpoint. Our sources do not give fixed versions for either Oracle flaw.

ClickHouse

The ClickHouse fix was merged into 26.9.1.702 and is included in 26.9 and later. The write-up says: "our exploit obtained an interactive shell as the clickhouse service account". An interactive shell means the attacker can type commands on the server as that account. Our sources do not give a CVE identifier for the ClickHouse issue.

Claimed versus confirmed

Statement Status
PostgreSQL flaw lets an object creator run code as the database's operating system user Confirmed by the PostgreSQL advisory
PostgreSQL fixed in 18.7, 17.12, 16.16, 15.20 and 14.25 Confirmed by the PostgreSQL advisory
ClickHouse fix included in 26.9.1.702 and later Confirmed in the ClickHouse project's merged pull request
ClickHouse exploit gave an interactive shell Claimed by the researchers
Oracle chain starts with no login Claimed by the researchers; Oracle details come from third-party trackers
MySQL affected versions, severity and fix Not known from our sources
Attacks in the wild None reported

Is anyone exploiting these database flaws?

Not that anyone has reported. The Hacker News, covering the research, says: "None has been seen in a real attack." That is a news report, not a guarantee. Now that the technique is public, waiting is the riskier choice.

What to do this week

Engine How to check your version What to install
PostgreSQL Run SELECT version(); 18.7, 17.12, 16.16, 15.20 or 14.25, matching your branch
ClickHouse Run SELECT version() 26.9.1.702 or later
MySQL Run SELECT version(); Compare with the CVE-2026-101786 advisory
Oracle ORDS Check the installed ORDS release If it is 24.2.0 to 26.2.1, follow Oracle's own guidance; we could not confirm a fixed release

Your checklist:

  1. List every database you run, including ones a vendor, developer or hosting provider runs for you. If someone else runs it, ask them which version you are on and when they will update it.
  2. Update PostgreSQL and ClickHouse to the versions in the table.
  3. Review who can create objects in PostgreSQL, such as functions and aggregates. If an application account does not need that ability, remove it.
  4. Run SHOW GRANTS, or your engine's equivalent, to see what each account can do. Treat the result as a starting point, not proof that you are safe.
  5. Limit who can reach ORDS and any other database HTTP endpoint. Only the networks that need it should be able to connect.
  6. Check what the database's operating system account can reach. If an attacker gets code running as that user, its access is their access.

Why this matters for a business network or website

A common assumption goes like this: if the website is hacked, the attacker only gets the website's database account, and that account is locked down. This research says a locked-down account can still lead to the server. Code running as the database's operating system user is no longer limited by the database's own permissions. From there, the server can be a stepping stone to the rest of your network.

The practical problem is often ownership. A database inside a hosted app, a vendor appliance or a container someone set up years ago is easy to forget. Our post on who is patching your servers covers how to settle that. A system that says it is up to date can still be running an old database engine underneath, which we explain in updated is not the same as patched. If you run your own servers, our self-hosting and infrastructure page explains how we set them up and keep them maintained.

Database RCE questions people are asking

What is a database RCE vulnerability?

It is a flaw that lets someone with database access get the database server to run commands of their choosing, outside the database itself.

Is PostgreSQL CVE-2026-116331 being exploited?

No attacks have been reported. The Hacker News says none has been seen in a real attack.

Which PostgreSQL version fixes CVE-2026-116331?

PostgreSQL 18.7, 17.12, 16.16, 15.20 and 14.25. Versions before those are affected.

Does a limited database user stop this kind of attack?

Not on its own. The researchers' point is that restrictive grants still leave much of the engine reachable. Keep permissions tight, and patch as well.

Which ClickHouse version is fixed?

The fix was merged into 26.9.1.702 and is included in 26.9 and later.

Is there a patch for the MySQL and Oracle flaws?

Our sources do not confirm fixed versions for MySQL CVE-2026-101786, Oracle Text CVE-2026-114819 or ORDS CVE-2026-91609. Check the vendors' advisories directly.

The bigger lesson

Permissions control what an account is supposed to do. Patches control what it can actually do when the software has a bug. A well-run database needs both, plus a clear answer to who updates it and when.

To have your databases and servers reviewed and kept patched, see security hardening or request a quote.

Get security alerts like this by email, along with the free checklist, at security alerts.

Sources: Depthfirst research; PostgreSQL CVE-2026-116331 advisory; MySQL security advisory; ClickHouse pull request; stack.watch CVE-2026-91609; isMalicious CVE-2026-114819; The Hacker News.

Share X LinkedIn Facebook

Was this article helpful?

We only keep the note with this article. No name, no email.

Protected by reCAPTCHA - Privacy and Terms.

Have a question about this article?

Ask it here and we will answer you directly by email. Questions are private, never posted.

Protected by reCAPTCHA - Privacy and Terms.

Security alerts by email

Hear about the next one first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.

Want a result like this?

Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.

Get a Tech Quote

Security alerts by email

The next security hole is already out there. Hear about it from us first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.