cve.bz

CVE-2026-116308 PostgreSQL dict_int reads beyond zero-length tokens

4.3 mediumEPSS 0.3%

Medium (4.3). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Buffer over-read in PostgreSQL dict_int allows a database user to disclose portions of server memory, via a zero-length token. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 22nd 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: partial, 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-126 Buffer Over-read
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-116308 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116308?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116308?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-116308 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-116308

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

HTML:

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

Fix and patched versions

Linux distributions

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

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

Red Hat's statement

This vulnerability is rated as Moderate because exploitation requires an authenticated database connection and the non-default dict_int extension to be installed in the target database. Under standard Red Hat enterprise deployments, this dictionary extension is not enabled by default, significantly limiting the exposure of typical installations. When the extension is present, an authenticated attacker can read adjacent server memory contents, but cannot modify database records or achieve arbitrary code execution.

Red Hat's mitigation

Remove the optional dict_int extension from databases where it is not strictly required, or restrict database access to prevent untrusted users from querying dictionaries that rely on this module.

To remove the extension from a specific database, execute the following SQL command as a superuser or database owner:

DROP EXTENSION IF EXISTS dict_int CASCADE;

Caveats: Dropping this extension removes any dependent full-text search configurations and will cause queries relying on dict_int to fail. Verify whether application schemas utilize this dictionary template prior to removal.

Service impact: Executing this command takes effect immediately within the database; restarting or reloading the PostgreSQL service is not required.

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

References

Check your stackJSON