cve.bz

CVE-2026-116323 PostgreSQL pltcl reentrant result conversion 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 pltcl allows an object creator to execute arbitrary code as the operating system user running the database, via a domain CHECK that re-enters the Tcl interpreter and frees or changes a string still used by the outer result conversion. 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-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-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-116323 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116323?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116323?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-116323 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-116323

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

HTML:

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

Fix and patched versions

Linux distributions

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

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 rates this vulnerability as Important because an authenticated user with permission to create database objects can achieve arbitrary code execution under the postgres operating system account. In standard Red Hat Enterprise Linux deployments, the PL/Tcl procedural language is neither installed nor enabled by default, significantly limiting exposure on typical systems. Risk is primarily confined to environments where the optional PL/Tcl subpackage is explicitly installed and untrusted users have been granted object creation privileges.

Red Hat's mitigation

If PL/Tcl is not required, remove the optional procedural language package or drop the extension from affected databases. Alternatively, restrict object creation permissions for untrusted database accounts.

1. To remove the optional PL/Tcl package:

# dnf remove postgresql-pltcl

2. To remove the extension from a specific database, execute the following SQL commands as a database administrator:

DROP EXTENSION IF EXISTS pltcl CASCADE;

DROP EXTENSION IF EXISTS pltclu CASCADE;

3. To prevent untrusted accounts from creating custom domains or objects, revoke schema creation privileges:

REVOKE CREATE ON SCHEMA <schema_name> FROM <username>;

Caveats:

Dropping the extension with CASCADE removes all dependent database functions, triggers, and objects implemented in PL/Tcl, which can impair application functionality. If package removal or administrative actions require reloading or restarting the PostgreSQL service (systemctl restart postgresql), active client connections will be terminated.

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

References

Check your stackJSON