cve.bz

CVE-2026-116316 PostgreSQL security-restricted operations can create types in pg_temp, which later queries of the session find

8.8 highEPSS 0.5%

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

On this page
Improper protection of alternate path in PostgreSQL security-restricted operations allows an object creator to execute arbitrary SQL as the operation's caller, via a domain, enum, or range type created in pg_temp. The victim session must later run a query containing an unqualified type name, e.g. "SELECT '1'::bigint"; autovacuum and other common security-restricted operation users do not do so, so they are unaffected. 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.5% estimated probability of exploitation activity in the next 30 days; 42nd 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-424 Improper Protection of Alternate Path
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
PostgreSQL (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

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

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

HTML:

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

Fix and patched versions

Linux distributions

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

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 has evaluated this vulnerability as having an Important impact because it allows an authenticated database user to gain elevated privileges and execute arbitrary SQL commands in the context of another session. In multi-tenant environments where multiple users connect to the same PostgreSQL instance, an attacker can create custom types in the temporary schema to hijack queries that omit schema qualification during security-restricted operations. While standard background maintenance tasks such as autovacuum do not execute queries with unqualified type casts and are unaffected, environments that allow untrusted users to connect and execute arbitrary database operations remain exposed.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

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

Attack patterns (CAPEC)

  • CAPEC-127 Directory Indexing Likelihood: High · Severity: Medium
  • CAPEC-554 Functionality Bypass Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON