CVE-2026-18447 · Runtime
NO FIX YET · SEE WHAT TO DO
A flaw in PostgreSQL SQL-language functions lets a user who can create database objects confuse types through an output parameter of type "any". The attacker 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.
Any PostgreSQL server before the fixed versions is exposed. The attacker must be able to create objects in the database, so servers where only trusted administrators can create functions are lower risk. Managed database services are handled by their provider.
Not affected if managed-hosting, no-untrusted-object-creators, patched-version
Who cares database, postgresql, self-hosted
psql -c "SHOW server_version;" and compare against the fixed versions below.CREATE functions in your databases.18.717.1216.1615.2014.25Type confusion in PostgreSQL SQL-language functions allows an object creator to execute arbitrary code as the operating system user running the database, via an output parameter of type "any". 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.