CVE-2026-116307 · Runtime
NO FIX YET · SEE WHAT TO DO
A use-after-free in PostgreSQL's plperl extension occurs when plperl is re-entered and a prepared query is freed while an outer call is still running it. 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.
Only servers running PostgreSQL versions before 18.7, 17.12, 16.16, 15.20 or 14.25 are affected. The flaw sits in the plperl procedural language, so systems that do not use plperl are likely not exposed. Exploitation requires the ability to create database objects, so tightly restricted databases carry less risk.
Not affected if patched-version, plperl-not-installed, restricted-object-creation
Who cares database, plperl, postgresql, self-hosted
psql -c "SHOW server_version;" and compare with the fixed versions below.psql -c "SELECT extname FROM pg_extension WHERE extname = 'plperl';"18.717.1216.1615.20Use after free in PostgreSQL plperl allows an object creator to execute arbitrary code as the operating system user running the database, via re-entering plperl and freeing a prepared query while an outer invocation is executing it. 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.
14.25