CVE-2026-120144 · Runtime
NO FIX YET · SEE WHAT TO DO
PostgreSQL mishandles a composite type change while its type-cache entry is being populated, causing type confusion. A user who can create database objects can execute 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.
Servers running PostgreSQL 18 with a minor version before 18.7 are affected. Any role that can create database objects such as composite types could exploit it, so limit who holds that privilege. Versions before PostgreSQL 18 are unaffected according to the sources.
Not affected if patched-18.7-or-later, postgresql-below-18
Who cares database, postgresql, self-hosted
psql -c 'SHOW server_version;' and confirm the version is inside major 18 and below 18.7postgres --version18.7 or laterType confusion from incomplete PostgreSQL type-cache invalidation allows an object creator to execute arbitrary code as the operating system user running the database, via a composite type change while its cache entry is being populated. Within major version 18, minor versions before PostgreSQL 18.7 are affected. Versions before PostgreSQL 18 are unaffected.
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.