CVE-2026-116306 · Runtime
NO FIX YET · SEE WHAT TO DO
A type confusion bug in PostgreSQL's composite-value field assignment lets a user who can create database objects change a composite type between deforming and reforming a value. The result is arbitrary code execution 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, since the flaw is in the core engine. The attacker must be able to create objects in the database, so exposure depends on who holds that privilege. Servers where only trusted administrators can create objects are at lower risk, but the sources do not say how common that setup is.
Not affected if patched-versions
Who cares database, postgresql, self-hosted
SELECT version(); in psql and compare against the fixed versions below.18.717.1216.1615.2014.25Type confusion in PostgreSQL composite-value field assignment allows an object creator to execute arbitrary code as the operating system user running the database, via changing a composite type between deforming and reforming a value. 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.