cve.bz

CVE-2026-116315 PostgreSQL tsvector_delete() heap buffer overflow 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
Heap-based buffer overflow in PostgreSQL tsvector_delete() allows a database user to execute arbitrary code as the operating system user running the database, via a tsvector whose lexeme data uses a nonstandard but valid ordering that requires additional alignment padding in the result. 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-122 Heap-based Buffer Overflow
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-116315 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116315?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116315?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-116315 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-116315

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

HTML:

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

Fix and patched versions

Linux distributions

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

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 rated this vulnerability as having an Important severity because an authenticated user can trigger a heap buffer overflow to execute arbitrary code with the permissions of the postgres service account, potentially compromising the host. While the impact on system integrity, confidentiality, and availability is high, exploitation requires valid database credentials and access to execute SQL functions, which prevents unauthenticated remote execution. In standard Red Hat Enterprise Linux deployments, exposure is further constrained by default SELinux policies that confine the PostgreSQL daemon and restrict access to broader system resources.

Red Hat's mitigation

Restrict network access to PostgreSQL to trusted hosts and clients only, limiting exposure to untrusted database users.

1. Restrict external network reachability to the PostgreSQL service using firewalld:

# firewall-cmd --permanent --remove-service=postgresql

# firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP_OR_SUBNET>

# firewall-cmd --reload

2. Configure /var/lib/pgsql/data/pg_hba.conf to only permit connections from authorized client addresses and trusted database roles, then reload the configuration:

# systemctl reload postgresql

Warning: Reloading firewall rules or the PostgreSQL service may temporarily interrupt active network connections. These operational controls reduce exposure by limiting network access to trusted clients, but they do not eliminate risk from authenticated users permitted to execute SQL queries.

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

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

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

References

Check your stackJSON