CVSS 3.1
8.8 highCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (8.8). EPSS 0.6% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain CVE-2026-116319 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116319?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116319?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116319 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | postgresql-15 | no fix listed | DEBIAN-CVE-2026-116319 |
| Debian | 13 | postgresql-17 | 17.12-0+deb13u1 | DEBIAN-CVE-2026-116319 |
| Debian | 14 | postgresql-18 | no fix listed | DEBIAN-CVE-2026-116319 |
| Ubuntu | 20.04:LTS | postgresql-12 | no fix listed | UBUNTU-CVE-2026-116319 |
| Ubuntu | 22.04:LTS | postgresql-14 | no fix listed | UBUNTU-CVE-2026-116319 |
| Ubuntu | 24.04:LTS | postgresql-16 | no fix listed | UBUNTU-CVE-2026-116319 |
| Ubuntu | 26.04:LTS, 26.10 | postgresql-18 | no fix listed | UBUNTU-CVE-2026-116319 |
| Ubuntu | Pro:14.04:LTS | postgresql-9.3 | no fix listed | UBUNTU-CVE-2026-116319 |
| Ubuntu | Pro:16.04:LTS | postgresql-9.5 | no fix listed | UBUNTU-CVE-2026-116319 |
| Ubuntu | Pro:18.04:LTS | postgresql-10 | no fix listed | UBUNTU-CVE-2026-116319 |
| Red Hat | hummingbird:1 | libpq, libpq-devel | 0:18.7-0.1.hum1 | RHSA-2026:99821 |
| Alpine | v3.21, v3.22 | postgresql15 | 15.20-r0 | ALPINE-CVE-2026-116319 |
| Alpine | v3.21, v3.22, v3.23 and 1 more | postgresql16 | 16.16-r0 | ALPINE-CVE-2026-116319 |
| Alpine | v3.21, v3.22, v3.23 and 1 more | postgresql17 | 17.12-r0 | ALPINE-CVE-2026-116319 |
| Alpine | v3.23, v3.24 | postgresql18 | 18.7-r0 | ALPINE-CVE-2026-116319 |
| Azure Linux | 3 | postgresql | no fix listed | AZL-113714 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpine.
Red Hat rates this Important.
This vulnerability is rated as having Important impact because an authenticated database user with permissions to define functions or objects can exploit a memory corruption flaw to achieve arbitrary code execution in the context of the postgres system user. While successful exploitation grants system-level access under the PostgreSQL process account, the PL/Perl procedural language extension is not enabled by default in standard Red Hat deployments. Consequently, systems that do not explicitly install and enable PL/Perl or that restrict object creation privileges to trusted administrators are not exposed to this issue.
Remove the optional PL/Perl package if it is not required by your applications:
# dnf remove postgresql-plperl
Alternatively, drop the PL/Perl extension from affected databases:
DROP EXTENSION IF EXISTS plperl CASCADE;
DROP EXTENSION IF EXISTS plperlu CASCADE;
If the extension is required, restrict execution privileges by revoking usage on the language from untrusted database roles:
REVOKE USAGE ON LANGUAGE plperl FROM PUBLIC;
Caveats: Dropping the extension or removing the package will break existing stored procedures and database applications that depend on PL/Perl. Revoking USAGE permissions prevents unprivileged users from executing PL/Perl functions.
Warning: Restarting or reloading the PostgreSQL service (e.g., `systemctl restart postgresql`) may be necessary to terminate existing database sessions and apply changes fully, which will temporarily interrupt active client connections.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | libpq | Affected | |
| Red Hat Hardened Images | postgresql17 | Affected | |
| Red Hat Hardened Images | postgresql18 | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-116319.