← All stories
● Covered by 2 sources · 3 reportsMedium impact3 neutral

22-Year-Old PostgreSQL Type-Confusion Bug Leads to Remote Code Execution

🔄 Updated 2d ago — new reporting from The Hacker News
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • A 22-year-old type-confusion bug found in PostgreSQL core.
  • Vulnerability allows remote code execution via memory corruption.
  • Exploit involves changing field types within composite data types.
  • Discovery stemmed from exploiting a PostgreSQL extension, pg_clickhouse.
  • PostgreSQL released updates addressing 52 security flaws.
  • The vulnerability is tracked as CVE-2026-6460.
  • The flaw affects all versions before 18.7, 17.12, 16.16, 15.20, and 14.25.
  • Full protection requires rebuilding C-language extensions.
  • The flaw has a CVSS score of 8.8.
  • The PostgreSQL Global Development Group has not reported any attacks using the flaw.
  • CISA's assessment lists exploitation as none.
  • The fix adds version checks to detect values that no longer match their type.
  • Security researcher Mehmet Ince described a working exploit for the flaw.
  • The researcher who demonstrated the exploits is Zheng Yu from Depthfirst.
  • The PostgreSQL flaw is tracked as CVE-2026-116331.

Discovery of a Long-Standing Vulnerability

A security researcher uncovered a 22-year-old zero-day vulnerability within the core of PostgreSQL. This flaw is categorized as a type-confusion vulnerability, which can lead to remote code execution.

Technical Details of the Exploit

The vulnerability is triggered by providing PostgreSQL with a value inside a composite type, then altering the type of one of its fields, and subsequently requesting PostgreSQL to read the value back. This manipulation causes a type confusion that results in a reliable memory-corruption exploit.

Origin of the Discovery

The discovery was not initially sought in PostgreSQL core but emerged from efforts to exploit the pg_clickhouse extension. While working on an exploit for pg_clickhouse, which involves translating ClickHouse values into PostgreSQL's native Datum format, questions arose about how PostgreSQL interprets its own data. This led to a deeper investigation into PostgreSQL's internal data handling mechanisms.

Impact and Context

This vulnerability represents a significant finding, as it allows for remote code execution in PostgreSQL, a widely used open-source relational database system. The researcher noted that this is the third part of a series on 'Systemic Risks in the Managed PostgreSQL Industry', indicating broader concerns within the ecosystem.

Updates

🕒 2026-11-19 · new reporting from The Hacker News
  • The researcher who demonstrated the exploits is Zheng Yu from Depthfirst.
  • The PostgreSQL flaw is tracked as CVE-2026-116331.
🕒 2026-11-13 · new reporting from The Hacker News
  • PostgreSQL released updates addressing 52 security flaws.
  • The vulnerability is tracked as CVE-2026-6460.
  • The flaw affects all versions before 18.7, 17.12, 16.16, 15.20, and 14.25.
  • Full protection requires rebuilding C-language extensions.
  • The flaw has a CVSS score of 8.8.
  • The PostgreSQL Global Development Group has not reported any attacks using the flaw.
  • CISA's assessment lists exploitation as none.
  • The fix adds version checks to detect values that no longer match their type.
  • Security researcher Mehmet Ince described a working exploit for the flaw.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 21

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

How outlets covered it

A researcher demonstrated remote code execution (RCE) exploits in PostgreSQL, MySQL, and Oracle databases, leveraging low-privilege accounts or no authentication to trigger memory-corruption bugs in the database engines. These exploits highlight that SQL permissions do not fully restrict access to underlying C/C++ engine code, allowing code execution even without access to application data.

PostgreSQL released updates addressing 52 security flaws, including CVE-2026-6460, a type confusion vulnerability present for 22 years. This flaw allows an authenticated database user with object creation privileges to execute code on the server, affecting all versions before 18.7, 17.12, 16.16, 15.20, and 14.25. Full protection requires rebuilding C-language extensions.

A 22-year-old type-confusion vulnerability in PostgreSQL core has been discovered, allowing for remote code execution. The flaw involves manipulating composite types and their field types, leading to reliable memory corruption when PostgreSQL attempts to read the altered values.