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.
The 5-Minute Cyber BriefDon’t Miss the Policy Changes That Affect Security Decisions
Get the key CISA actions, new regulations, guidance, and risk shifts in a quick daily brief.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
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.
- Affected: every version before 18.7, 17.12, 16.16, 15.20 and 14.25. Older major versions also have the bugs and get no fix.
- Severity: the project scores CVE-2026-6460 at 8.8. The Hacker News counts 32 of the 52 fixes at that same score.
- Client tools: fixes include a crafted archive that makes pg_restore run code (CVE-2026-116314) and a tar dump that can make psql run commands (CVE-2026-116330).
- End of life: 14.25 is the last PostgreSQL 14 release.
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
- Run
SELECT version();on each server and plan the minor update for your major version: 18.7, 17.12, 16.16, 15.20 or 14.25. - Rebuild or update every C-language extension at the same time. The project’s package maintainers warn that extensions built against older releases still load but may not be protected.
- Update pg_dump, pg_restore, psql, reindexdb and vacuumdb on every machine that runs them, including backup servers and laptops.
- Follow the release notes’ reindexing steps, and take a new full backup if you use incremental backups.
- Leave the new
composite_type_mismatchsetting alone. The project says turning off its checks carries security risks.
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
- CVE-2026-6460: type confusion after ALTER … SET DATA TYPE executes arbitrary code. CVSS 3.1: 8.8 (AV:N/AC:L/PR:L/UI:N). Fixed November 12 in 18.7, 17.12, 16.16, 15.20 and 14.25.
- CVE-2026-116314: pg_restore runs code from a crafted non-plain archive (8.8). CVE-2026-116330: pg_dump tar restore.sql fails to block psql command injection (8.8).
- CVE-2026-116322: a pre-authentication cancel request can leak a spinlock (5.3); The Hacker News says it is the one server bug that needs no login.
- Exploitation: none reported by the project; CISA lists exploitation as none in the CVE record.
Hunt / verify
- List superuser and CREATEDB roles with
SELECT rolname FROM pg_roles WHERE rolcreatedb OR rolsuper;, then check which roles have CREATE on the schemas your apps use. - Check database logs for unexpected server crashes and restarts since early November.
- Check container images and CI base images for pinned PostgreSQL versions older than the fixed releases.
Source: PostgreSQL CVE-2026-6460; Release announcement
Sources
- PostgreSQL: CVE-2026-6460 type confusion after ALTER … SET DATA TYPE
- PostgreSQL: 18.7, 17.12, 16.16, 15.20, 14.25 and 19 RC 2 released
- The Hacker News: PostgreSQL patches 52 flaws, including 22-year-old bug enabling authenticated RCE
- Mehmet Ince: turning a 22-year-old PostgreSQL type-confusion primitive into RCE (part 3)
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.