PostgreSQL · Public exploit code

[Single source] Researcher Publishes RCE PoCs for PostgreSQL, MySQL, ClickHouse and Oracle

· 1 min read

A researcher published proofs of concept that run code on database servers from low-privilege accounts, via memory-corruption bugs in the SQL engine. The PoCs target PostgreSQL, MySQL and ClickHouse, plus a separate Oracle chain. Restrict database account permissions and track vendor patches.

Illustration: Researcher Publishes RCE PoCs for PostgreSQL, MySQL, ClickHouse and Oracle
WhatsApp LinkedIn X
HighVulnerabilityPublic exploit codeFix unconfirmed

In 30 seconds

thehackernews.com
Observed

A researcher has published proof-of-concept exploits that, according to a report from The Hacker News dated November 19, 2026, run code on a database server starting from a low-privilege account that cannot read a single application table. The exploits went public one day before the report and target PostgreSQL, MySQL and ClickHouse, with a separate chain for Oracle, by reaching memory-corruption bugs in the engine code behind ordinary SQL.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

What happened

Observed

Publication came first. Per the report, the researcher released the exploits one day before the coverage appeared, and the release is described as the researcher's own proofs of concept against PostgreSQL, MySQL and ClickHouse, plus a separate chain aimed at Oracle.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Alleged

The claimed chain inside each exploit runs like this: an account with minimal permissions issues ordinary SQL, the query reaches memory-corruption bugs in the database engine's own code, and the result is code execution on the server hosting the database, no table reads required. As the report frames it, an account that cannot touch the application's data can still compromise the machine that holds it.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Why it matters

Inferred

Code execution on a database server usually outclasses any permission scheme, because the process that enforces who can read which table is the very process an attacker would now control. If the demonstration holds up, the common assumption that a low-privilege SQL account is a safe account takes a serious hit.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Inferred

There is also the surface-area problem. PostgreSQL, MySQL, ClickHouse and Oracle sit under a huge share of the world's applications, and this line of research treats the query language itself, not the data, as the attack surface, meaning every path an engine exposes through a normal query becomes a place where a memory bug can live.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

What to do

Inferred

The immediate practical step is to shrink exposure: inventory every account that can open a connection and run arbitrary SQL, revoke the ones with no business need, and stop treating read-only or low-privilege logins as harmless. The premise of the research is that any of them can be a foothold.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Inferred

Then watch for fixes. The proofs of concept are public, which lowers the effort for anyone who already has a toehold, so advisories and patches for the affected engines belong at the top of the queue the moment they land.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Confirmed and still uncertain

Observed

Established by the available report: the PoCs exist and are public, they cover PostgreSQL, MySQL and ClickHouse with a separate Oracle chain, and the researcher claims code execution from accounts that cannot read application tables by hitting memory bugs behind ordinary SQL.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Inferred

Still open: the researcher's name, the specific functions or versions affected, whether the bugs are new or already patched, whether vendors received advance notice, and whether anything has been exploited in the wild. The evidence text also cuts off mid-sentence while describing what the Oracle chain requires, so that detail is simply missing here.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

What people are saying

Observed

The only voice in this batch is the security press itself. The Hacker News attributes the findings to a researcher it does not name, and no vendor statement, advisory, or independent reproduction appears alongside it yet.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Evolution

Observed

The story currently sits at its first snapshot: exploits published one day, a press report the next. There is no earlier disclosure history, advisory, or fix cycle in the evidence to trace.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Inferred

The likely next beats are vendor responses, patches, and independent testing of the PoCs, none of which exist in the current record, so treat the picture as early and likely to shift.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Reach

Observed

1 independent groups, 1 updates, and 0 engagements.

Technical detail

Alleged

Mechanically, the claim is that ordinary SQL from a low-privilege account reaches buggy code inside the database engine, the kind of memory-corruption flaw that corrupts the engine's internal state, and the end result is code running on the server itself rather than just query results coming back.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Observed

Named scope: PostgreSQL, MySQL and ClickHouse for the main proofs of concept, with Oracle addressed by a separate chain. The report does not specify versions, vulnerable components, or the prerequisites of that Oracle chain.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Sources and evidence

Observed

This brief rests on one item: the The Hacker News article published November 19, 2026, delivered via RSS and marked as primary evidence, with a credited image. It is press coverage of a researcher's demonstration, not a vendor advisory, a bug report, or the PoC code itself, and the article text arrived truncated in this batch.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Inferred

That single-source footing is the main caveat. Everything about impact and exploitability rests on one outlet relaying one researcher's work, and closing the open questions above will require primary documents: advisories, patches, or the published exploits.Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rssOpen original sourceSee in source list

Sources

  1. Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclethehackernews.com · rss

Incidents like this, every morning

The ones that need action first, in a 3-minute read.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Get the next one tomorrow morning

One email a day with what changed, what to fix first and how.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Share it with your team

Whoever handles security with you should get it too.

LinkedIn X

Your colleague gets a confirmation request. Nothing is sent unless they confirm.

See all news

Read also

Before you go: get this every day

The HIFY Radar daily edition lands every morning with the incidents that need action. Free.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click