CVE-2026-116304 · Runtime
NO FIX YET · SEE WHAT TO DO
A use-after-free flaw in how PostgreSQL parallel workers share anonymous RECORD type descriptors lets one process free memory another still uses. A database user with login rights can run arbitrary code as the operating system user running the database.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Any PostgreSQL server before the fixed versions is affected. The attacker needs a database login, and the flaw is reached through queries that use parallel workers, so servers where users have no database access are much less exposed. Teams running managed PostgreSQL should check with their provider.
Not affected if managed-hosting, no-untrusted-db-users
Who cares database, postgresql, self-hosted
SELECT version(); in psql and compare against the fixed versions below.postgres --version.18.717.1216.1615.2014.25Use after free in PostgreSQL coordination of anonymous RECORD type identifiers among parallel workers allows a database user to execute arbitrary code as the operating system user running the database, via causing one process to free a shared tuple descriptor while another process retains and later uses its address. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.