Research · 3 min read
PostgreSQL’s November updates fix 52 flaws, including a 22-year-old bug
A database user who can create objects may be able to run code as the account that runs PostgreSQL. The project has not reported attacks. C extensions have to be rebuilt with the server.

If you run PostgreSQL, the updates published on November 12, 2026 are a security release, not a routine bump. The Hacker News reported them on November 13. One of the 52 flaws, CVE-2026-6460, is scored 8.8. The project has not reported attacks using it. CISA’s note in the CVE record, as The Hacker News describes it, lists exploitation as none.
What the serious flaw needs
CVE-2026-6460 is a type confusion in composite types, which are types built from named fields. A field’s type can be changed while older values of that type are still held elsewhere in the server. The server could then read an old value as if it had the new type. The fix adds version checks so a mismatch can be seen.
The Hacker News, citing the project, says someone who can create objects may be able to run code with the rights of the operating system user that runs PostgreSQL. Versions before 18.7, 17.12, 16.16, 15.20 and 14.25 are affected. Red Hat’s assessment, as reported, says the person needs a database login that can create or modify objects. The project does not say that a default login, with no extra rights, can go past a crash to running a command.
Researcher Mehmet Ince, credited by the project on this flaw and five others in the same release, traces the ability to change a column’s type to May 5, 2004. The Hacker News says his method for running code depends on a later change from 2015, and that he shared proofs with several managed-database teams in August, including AWS, Microsoft, Google, Supabase, Databricks and Ubicloud. The write-up does not say which of those services are patched today.
Thirty-two of the 52 flaws are scored 8.8, the highest in the release. Only one, CVE-2026-116322, needs no login: an unauthenticated client can restart a PostgreSQL 18 server. Separate fixes cover client tools. A crafted archive can make pg_restore run code as the person running it. A compromised source server can make psql run code through a restore script in pg_dump output.
What you can do
- Update the server to 18.7, 17.12, 16.16, 15.20 or 14.25, matching the major version you run. PostgreSQL 14 is now at end of life, and 14.25 is its last release. Older majors were affected and did not get an update.
- Rebuild C-language extensions at the same time. The project’s packaging notes, as reported, say extensions built against older releases may still load and may not be protected. Some need source changes. Extensions built for the new releases can fail on an older server.
- Restart PostgreSQL if it is not started by its own service unit, for example under Patroni, right after the update.
- Update client tools such as
pg_dump,pg_restore,reindexdbandvacuumdbon every machine that runs them. - Do not turn off the new type check. The project says the setting that disables it carries security risks, and the release notes offer no workaround for a server you cannot update yet.
- Afterward, follow the reindexing steps in the release announcement. If you use incremental backups, take a new full backup and base later incrementals on it.
If you only use an app that sits on Postgres
You do not patch the database. The company that runs it does. Nothing in this release asks you to click a link or reset a personal password.
How Frame helps
Frame can also look up your verified emails in Have I Been Pwned’s breach database. This is a database update, not a list of personal addresses. Frame doesn’t scan database servers.
Sources
- The Hacker News, PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE, November 13, 2026
More stories
New posts, by email.
About once a month. Plain-language privacy notes, nothing else. I never share your address.


