CVE-2026-120150 · Runtime
NO FIX YET · SEE WHAT TO DO
A memory-handling bug in PostgreSQL's expanded-record domain checks lets a user who can create database objects run arbitrary code. The code runs as the operating system user that runs the database server.
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.
Servers running PostgreSQL versions before 18.7, 17.12, 16.16, 15.20, or 14.25 are affected. The attacker must be able to create objects in the database, such as domains and composite types, so databases where only trusted administrators can create objects are lower risk. Managed hosting providers patch on their own schedule, so check their notices.
Not affected if managed-hosting, patched-version
Who cares database, postgresql, self-hosted
SELECT version(); in psql and compare against the fixed releases below.postgres --version.18.717.1216.1615.2014.25Use after free in PostgreSQL expanded-record domain checks allows an object creator to execute arbitrary code as the operating system user running the database, via repeated checks of a domain over a composite type that cause reuse of a dangling memory-context pointer. 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.