cve.bz

CVE-2026-116307 PostgreSQL plperl prepared-query use-after-free executes arbitrary code

8.8 highEPSS 0.6%

High (8.8). EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
Use 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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.6% estimated probability of exploitation activity in the next 30 days; 49th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
Assigned by
PostgreSQL (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-116307 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116307?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116307?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-116307 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.

Badge for a README or a site

CVE-2026-116307

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-116307](https://cve.bz/cve/badge/CVE-2026-116307.svg)](https://cve.bz/cve/CVE-2026-116307)

HTML:

<a href="https://cve.bz/cve/CVE-2026-116307"><img src="https://cve.bz/cve/badge/CVE-2026-116307.svg" alt="CVE-2026-116307"></a>

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12postgresql-15no fix listedDEBIAN-CVE-2026-116307
Debian13postgresql-1717.12-0+deb13u1DEBIAN-CVE-2026-116307
Debian14postgresql-18no fix listedDEBIAN-CVE-2026-116307
Ubuntu20.04:LTSpostgresql-12no fix listedUBUNTU-CVE-2026-116307
Ubuntu22.04:LTSpostgresql-14no fix listedUBUNTU-CVE-2026-116307
Ubuntu24.04:LTSpostgresql-16no fix listedUBUNTU-CVE-2026-116307
Ubuntu26.04:LTS, 26.10postgresql-18no fix listedUBUNTU-CVE-2026-116307
UbuntuPro:14.04:LTSpostgresql-9.3no fix listedUBUNTU-CVE-2026-116307
UbuntuPro:16.04:LTSpostgresql-9.5no fix listedUBUNTU-CVE-2026-116307
UbuntuPro:18.04:LTSpostgresql-10no fix listedUBUNTU-CVE-2026-116307
Red Hathummingbird:1libpq, libpq-devel0:18.7-0.1.hum1RHSA-2026:99821
Alpinev3.21, v3.22postgresql1515.20-r0ALPINE-CVE-2026-116307
Alpinev3.21, v3.22, v3.23 and 1 morepostgresql1616.16-r0ALPINE-CVE-2026-116307
Alpinev3.21, v3.22, v3.23 and 1 morepostgresql1717.12-r0ALPINE-CVE-2026-116307
Alpinev3.23, v3.24postgresql1818.7-r0ALPINE-CVE-2026-116307
Azure Linux3postgresqlno fix listedAZL-113687

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

Red Hat rates this Important.

Red Hat's statement

Red Hat Product Security rates this vulnerability as Important because authenticated accounts permitted to define custom database objects can execute shell commands under the PostgreSQL service account. The impact does not reach Critical severity because exploitation requires existing database access along with specific object creation permissions, and the PL/Perl language extension is not enabled in standard deployments by default. Environments remain unaffected unless administrators explicitly install and activate PL/Perl and grant object-definition rights to untrusted users.

Red Hat's mitigation

To mitigate this vulnerability, disable the PL/Perl procedural language extension or remove its subpackage if PL/Perl functions are not required:

1. Drop the PL/Perl extension from affected databases:

```sql

DROP EXTENSION IF EXISTS plperl CASCADE;

DROP EXTENSION IF EXISTS plperlu CASCADE;

```

2. Alternatively, revoke language usage privileges from untrusted roles:

```sql

REVOKE USAGE ON LANGUAGE plperl FROM PUBLIC;

```

3. If PL/Perl is entirely unused across the host, uninstall the optional subpackage:

```sh

# dnf remove postgresql-plperl

```

Caveats:

- Dropping the extension or removing the subpackage will cause any database queries or stored procedures relying on PL/Perl to fail.

- Using CASCADE will recursively drop all database objects (such as functions and triggers) that depend on PL/Perl.

- Warning: Modifying system packages or stopping the database service for maintenance may require a service reload or restart (`systemctl restart postgresql`), which will disconnect active client sessions and cause temporary database unavailability.

ProductPackageStateAdvisory
Red Hat Hardened ImageslibpqAffected
Red Hat Hardened Imagespostgresql17Affected
Red Hat Hardened Imagespostgresql18Affected

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-116307.

References

Check your stackJSON