PostgreSQL CVE-2026-6460 (CVSS 8.8): A 22-Year-Old Type Confusion Bug Lets Database Users Run Code on the Server — 52 Flaws Fixed in 18.7, 17.12, 16.16, 15.20 and 14.25

DevSecOps · 2026-11-15 · By H.A

PostgreSQL CVE-2026-6460 (CVSS 8.8): A 22-Year-Old Type Confusion Bug Lets Database Users Run Code on the Server — 52 Flaws Fixed in 18.7, 17.12, 16.16, 15.20 and 14.25

PostgreSQL's 12 November release fixes 52 security issues, led by CVE-2026-6460, a type confusion bug dating back to 2004 that lets any user who can create objects run code as the postgres OS account, with no workaround available.

PostgreSQL has shipped one of the largest security releases in its history. On 12 November 2026 the project published versions 18.7, 17.12, 16.16, 15.20 and 14.25, fixing 52 security issues across the server and its client tools. The headline flaw, CVE-2026-6460, is a type confusion bug whose roots go back to a feature added in May 2004. A database user who can create objects can use it to run code on the server.

What Happened

The project's security page lists CVE-2026-6460 with a CVSS v3 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and the description "Type confusion after ALTER ... SET DATA TYPE executes arbitrary code". It affects every supported major version, 14 through 18. Older major versions that no longer get updates are also vulnerable.

Of the 52 fixes, 32 carry the same 8.8 score, which is the highest rating in this release. Security researcher Mehmet Ince is credited with CVE-2026-6460 and five other flaws. More than a dozen reporters are credited in total.

PostgreSQL 14 reached end of life with this release, so 14.25 is the last update that branch will ever get.

Technical Details

The bug is in how PostgreSQL handles composite types, which are row-like types made up of named fields. When the type of a field is changed with ALTER ... SET DATA TYPE, older values stored in the previous format can still exist elsewhere in the server. PostgreSQL can then read one of those old values as if it had the new type. That kind of type confusion lets an attacker corrupt memory in a controlled way.

The ability to change a column's type arrived on 5 May 2004. The technique that turns the confusion into code execution relies on a change made in May 2015. Ince's public writeup, demonstrated on PostgreSQL 18.6, shows SQL that crashes an unpatched server and a step that leaks memory addresses. It deliberately leaves out the final step that runs a command.

The code runs with the privileges of the operating system account that runs PostgreSQL, usually postgres. From there an attacker can read every database on the cluster, tamper with data, or try to move further into the host.

Other fixes worth noting:

Who Is Affected

There is an open question about the minimum privilege needed. Red Hat says an attacker needs a login that can create or modify objects. It is not yet clear whether an account with only default privileges can get past the crash to code execution.

Patch Status

Fixed versions are 18.7, 17.12, 16.16, 15.20 and 14.25 (19 RC 2 also received the fixes). The project says it knows of no attacks, and CISA lists exploitation as none. There is no workaround for servers that can't be updated yet.

What To Do Now

-- See which roles can create objects in each schema
SELECT n.nspname, r.rolname
FROM pg_namespace n CROSS JOIN pg_roles r
WHERE has_schema_privilege(r.oid, n.oid, 'CREATE')
  AND n.nspname NOT LIKE 'pg_%' AND n.nspname <> 'information_schema';

-- Confirm the running server version after patching
SELECT version();

Why It Matters

A 22-year-old bug in one of the most carefully reviewed open-source databases shows how long subtle memory-safety issues can go unnoticed in mature C code. A bug that needs a login is easy to dismiss, but in many real deployments "an authenticated user who can create a table" includes web application accounts, analysts, tenants and anyone who has phished a developer. With a partial public writeup already available, the gap between "no known attacks" and real-world exploitation could close quickly. Patch the servers, the extensions and the client tools together.

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Your watchlist

    Follow threat actors, malware, CVEs and vendors — we tell you when a new report, CVE record or exploitation alert mentions them.

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Privacy Policy

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Investigate any domain, IP, URL, file hash, email or CVE in one search, plus breach and password checks, hash identification and a payload cheatsheet.

    Outage Monitor

    Is Microsoft 365, Facebook, Google, AWS or ChatGPT down? Live status of the big tech services from their official status pages, every incident with its full timeline, and how long each one took to fix.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.

    SIGNAL LOST

    We couldn't find this page

    The page may have been moved or deleted, or the address was mistyped.