CVE-2026-116319 · Runtime
NO FIX YET · SEE WHAT TO DO
PostgreSQL's plperl extension has a use-after-free bug triggered by reentrant return_next() calls. 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 versions before 18.7, 17.12, 16.16, 15.20, or 14.25 are affected, and the risk is highest where plperl is installed and untrusted users can create database objects. Systems without the plperl extension, or where only trusted administrators create objects, are less exposed. The sources do not say whether the fix is available for every branch beyond those listed.
Not affected if plperl-not-installed, trusted-users-only
Who cares database, plperl, postgresql, self-hosted
postgres --version or SELECT version();SELECT * FROM pg_extension WHERE extname = 'plperl';18.7, 17.12, 16.16, 15.20, or (per the affected ranges given: versions before these are affected)Use after free in PostgreSQL plperl allows an object creator to execute arbitrary code as the operating system user running the database, via reentrant return_next() calls. 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