PostgreSQL 22-Year-Old Type-Confusion Primitive Turned into Remote Code Execution
Is it fixed? Not yet.
Ongoing since Nov 12, 18:22 UTC. First reported Nov 12, 18:22 UTC.
What happened
PostgreSQL has patched 52 flaws, including a 22-year-old bug (CVE-2026-6460) that has been successfully turned into an authenticated remote code execution vulnerability via a type-confusion primitive.
What caused it?
A type-confusion primitive present for 22 years was exploited to achieve remote code execution.
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Timeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on Hacker News thread
22-Year-Old PostgreSQL Bug Turned into Remote Code Execution
Source - Confirmed on Lobste.rs thread
How I Ended Up Turning a 22-Year-Old PostgreSQL Type-Confusion Primitive into RCE (CVE-2026-6460)
Source - Confirmed on Bluesky post
PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE
Source - Status changed
Status changed: investigating → trending (3 independent sources, BVS 69.8).
Evidence
3 reports · 1 HN, 1 Lobsters, 1 BlueskyShow
- [1]HN First report22-Year-Old PostgreSQL Bug Turned into Remote Code Execution(opens Hacker News thread in a new tab)
by ozirus 133upvotes 16comments
- [2]LobstersHow I Ended Up Turning a 22-Year-Old PostgreSQL Type-Confusion Primitive into RCE (CVE-2026-6460)(opens Lobste.rs thread in a new tab)
by sjamaan 2upvotes 1comments92% match
- [3]BlueskyPostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE(opens Bluesky post in a new tab)
PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE
by infosec.skyfleet.blue 0upvotes 0comments92% match
FAQ
What happened in the PostgreSQL issue?
PostgreSQL has patched 52 flaws, including a 22-year-old bug (CVE-2026-6460) that has been successfully turned into an authenticated remote code execution vulnerability via a type-confusion primitive.
What is affected by the PostgreSQL issue?
PostgreSQL.
When did the PostgreSQL issue start and end?
It started Nov 12, 18:22 UTC and is still ongoing (6 d 10 h so far). This page updates as it develops.
How do I get alerts for PostgreSQL?
Subscribe to the PostgreSQL RSS feed for every new PostgreSQL incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether PostgreSQL is down. PostgreSQL feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 3 reports from 3 independent sources.