cve.bz

CVE-2026-116326 PostgreSQL plperl tied-object exceptions follow stale sigjmp_buf

8.8 highEPSS 0.6%

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

On this page
Uncaught exceptions in PostgreSQL plperl allow an object creator to cause use of a stale sigjmp_buf, via a tied Perl object, or a Perl object whose overloaded conversion throws while plperl is handling another error. We have not ruled out arbitrary code execution on some platform. 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; 51st 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-13. 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-672 Operation on a Resource after Expiration or Release
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-116326 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116326?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116326?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-116326 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-116326

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-116326](https://cve.bz/cve/badge/CVE-2026-116326.svg)](https://cve.bz/cve/CVE-2026-116326)

HTML:

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

Fix and patched versions

Linux distributions

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

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

This vulnerability is rated as Important severity because an authenticated database user with privileges to execute or define PL/Perl functions could achieve arbitrary code execution within the context of the PostgreSQL backend process. However, the PL/Perl procedural language is an optional component that is not enabled by default on standard Red Hat Enterprise Linux PostgreSQL deployments. Environments that do not install the optional plperl subpackage or grant untrusted users access to PL/Perl are not exposed to this flaw.

Red Hat's mitigation

Disable or restrict access to the PL/Perl extension in affected databases, or remove the optional PL/Perl package if not required.

1. Restrict PL/Perl language usage from untrusted database roles:

```sql

REVOKE USAGE ON LANGUAGE plperl FROM PUBLIC;

REVOKE USAGE ON LANGUAGE plperlu FROM PUBLIC;

```

2. If PL/Perl is not required, drop the extension from affected databases:

```sql

DROP EXTENSION IF EXISTS plperl CASCADE;

DROP EXTENSION IF EXISTS plperlu CASCADE;

```

3. Optionally, remove the RPM package providing the language integration:

```bash

dnf remove postgresql-plperl

```

Caveats:

Revoking access or dropping the extension will break existing database stored procedures and functions that rely on PL/Perl.

Warning:

Database-level privilege and extension changes do not require restarting the postgresql service, but active client sessions should be terminated to enforce privilege revocations immediately.

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

References

Check your stackJSON