PostgreSQL fixed 52 security bugs, one that lets a database user run code. Update and rebuild your extensions

By George Bailey   Published: 11/16/26   4 min read

The PostgreSQL project released 18.7, 17.12, 16.16, 15.20 and 14.25 on November 12. The update closes 52 security bugs. The one getting attention, CVE-2026-6460, lets a database user who can create objects run code on the server as the operating system account that runs PostgreSQL.

Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.

This one takes more than a package update. The project says C-language extensions need to be rebuilt against the new release, and some post-update steps involve reindexing.

PostgreSQL fixed 52 security bugs in one release. Update the server, rebuild your C extensions, and update pg_dump and pg_restore on every machine that runs them.

PostgreSQL ships fixes for 52 security bugs at once

CVE-2026-6460 is a type confusion bug. If a column’s data type changes while old values of that type are still held elsewhere in the server, PostgreSQL can read the old value as if it had the new type. Researcher Mehmet Ince traced the root of it to a feature added in 2004 and published a write-up showing a crash and a memory leak on PostgreSQL 18.6. He left out the final step that runs a command.

Any database where users or apps can create objects

Most of these bugs need a database login, so the first question is who can create tables, types or functions on your servers. Apps with broad database rights, shared analytics databases and anything that lets customers run SQL are the risky ones.

No attacks have been reported, and CISA’s note in the CVE record lists exploitation as none. Ince says he shared proofs of concept with managed providers including AWS, Microsoft Azure and Google AlloyDB in August. Their current patch status isn’t public, so ask your provider.

Move to 18.7, 17.12, 16.16, 15.20 or 14.25 and rebuild C extensions

Forward this

For whoever runs our databases: PostgreSQL released an update that fixes 52 security bugs, one of which lets a database user run code on the server. Can we schedule the minor-version update, rebuild extensions, and update the backup tools that use pg_dump and pg_restore? If we use a managed PostgreSQL service, can we ask the provider when they will be on the new release?

Details

Hunt / verify

Source: PostgreSQL CVE-2026-6460; Release announcement

Sources

George Bailey

George Bailey is the byline of the CyberExperts editorial desk, the team behind the CyberExperts Daily Brief. The desk covers vulnerabilities, breaches and security news from vendor advisories, CISA alerts and other primary sources, and links those sources in every story. Questions or corrections: [email protected].