Written November 16, 2026, from the PostgreSQL project’s announcement and public reporting. We will update it as more information comes out.
If your business uses PostgreSQL, a popular open-source database, your IT person or hosting provider should be reading this week’s security release. This post explains what changed, who has to act, and what to check. If your website runs on MySQL or MariaDB, as most small business sites do, this specific update doesn’t apply, but the same habits do.
What happened
On November 12 the PostgreSQL project released versions 18.7, 17.12, 16.16, 15.20 and 14.25, which together fix 52 security flaws. The most serious one is CVE-2026-6460, rated 8.8 out of 10. It lets a database user who can create objects run code on the server, with the rights of the operating system account that runs PostgreSQL. The weakness has existed for about 22 years. thehackernewsthehackernews
The project has not reported any attacks that use it. But a researcher has published a technical writeup showing how to crash an unpatched server, although not the final step that runs a command. Once details are public, waiting gets riskier. thehackernewsthehackernews
It isn’t the only one. 32 of the 52 flaws are rated 8.8, one lets an unauthenticated client restart PostgreSQL 18 servers, and others sit in tools such as pg_restore and psql. thehackernews
Who has to patch?
The PostgreSQL project has released the fix. Nothing installs it automatically.
Your own server: you or your IT person.
A cloud database (AWS, Azure, Google, Supabase and others): the provider applies updates, but you may need to accept or schedule one. The researcher worked with these providers privately, but his writeup doesn’t give each service’s current patch status. Check each one’s notices. thehackernews
A hosting company: ask them.
Business software that includes PostgreSQL (ERP systems such as Odoo, hotel, HR, or point-of-sale systems): ask the vendor.
Why patching alone may not be enough
Extensions. Full protection requires rebuilding or updating every C-language extension on the server. PostGIS and similar add-ons are common examples. thehackernews
Client tools. pg_dump, pg_restore, and psql also need the update on every machine that runs them, including your backup scripts.
Reindexing. Some fixes require you to rebuild certain indexes after updating, and if you use incremental backups, you should take a new full backup. The release announcement lists the exact cases. postgresqlpostgresql
Who can create objects. The main flaw needs a login that can create objects. If your application’s database account has that power, a stolen password or a flaw in the web app could turn into control of the server. Give applications only the read and write rights they need.
A simple update plan (for your IT person)
Find your version:
psql -c "SELECT version();"Back up, and check that the backup restores.
Update to the fixed version for your major version, for example 17.x to 17.12.
Restart the service. The new code only runs after a restart, so plan a short downtime.
Update extensions and client tools.
Follow the reindexing steps in the release announcement, and take a new full backup if you use incremental backups.
Review who can create objects, and remove it where it isn’t needed.
PostgreSQL 14 has reached end of life, so any server on it needs a plan to move to a supported version. windowsforum
Questions to ask your developer or host
Which PostgreSQL version do we run, and is it patched?
Do we use any extensions, and have they been updated?
Do our application accounts need the right to create objects?
Can you show me a recent backup restore test?
When is the update scheduled, and is there downtime?
What we don’t know yet
The sources do not say whether an account with only default privileges can go beyond a crash to running code. The project’s advisory offers no workaround for servers that can’t be updated, so updating is the real fix. We’ll update this post if the picture changes. thehackernewsthehackernews
Want a second pair of eyes?
At Northgate IT Consultancy we check the version, access, and backups behind a business’s databases and servers as part of our Cloud and Infrastructure Review. Send us a message at northgate-it.com.ph/contact. A short call is free.