CVSS 3.1
7.2 highCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HCVE-2026-116313 PostgreSQL "vacuumdb --missing-stats-only" lets a database owner execute code as the vacuumdb user
High (7.2). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
On this page
Untrusted search path in PostgreSQL vacuumdb allows a database owner to execute arbitrary SQL as the database user running vacuumdb, via shadowing operators used in the --missing-stats-only catalog query. The pg_upgrade documentation recommends an affected vacuumdb invocation. Within major version 18, minor versions before PostgreSQL 18.7 are affected. Versions before PostgreSQL 18 are unaffected.
Severity
- EPSS
- 0.5% estimated probability of exploitation activity in the next 30 days; 43rd 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-426 Untrusted Search Path
- OWASP Top 10
- A08:2025 Software or Data Integrity Failures
- Published
- Modified
- Assigned by
- PostgreSQL (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-116313 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116313?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116313?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-116313 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
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:
[](https://cve.bz/cve/CVE-2026-116313)
HTML:
<a href="https://cve.bz/cve/CVE-2026-116313"><img src="https://cve.bz/cve/badge/CVE-2026-116313.svg" alt="CVE-2026-116313"></a>
Fix and patched versions
- Red Hat, Alpine: fixed package versions per release
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | postgresql-18 | no fix listed | DEBIAN-CVE-2026-116313 |
| Ubuntu | 20.04:LTS | postgresql-12 | no fix listed | UBUNTU-CVE-2026-116313 |
| Ubuntu | 22.04:LTS | postgresql-14 | no fix listed | UBUNTU-CVE-2026-116313 |
| Ubuntu | 24.04:LTS | postgresql-16 | no fix listed | UBUNTU-CVE-2026-116313 |
| Ubuntu | 26.04:LTS, 26.10 | postgresql-18 | no fix listed | UBUNTU-CVE-2026-116313 |
| Ubuntu | Pro:14.04:LTS | postgresql-9.3 | no fix listed | UBUNTU-CVE-2026-116313 |
| Ubuntu | Pro:16.04:LTS | postgresql-9.5 | no fix listed | UBUNTU-CVE-2026-116313 |
| Ubuntu | Pro:18.04:LTS | postgresql-10 | no fix listed | UBUNTU-CVE-2026-116313 |
| Red Hat | hummingbird:1 | libpq, libpq-devel | 0:18.7-0.1.hum1 | RHSA-2026:99821 |
| Red Hat | hummingbird:1 | postgresql17, postgresql17-docs, postgresql17-test and 12 more | 0:17.11-1.2.hum1 | RHSA-2026:80584 |
| Alpine | v3.21, v3.22 | postgresql15 | 15.20-r0 | ALPINE-CVE-2026-116313 |
| Alpine | v3.21, v3.22, v3.23 and 1 more | postgresql16 | 16.16-r0 | ALPINE-CVE-2026-116313 |
| Alpine | v3.21, v3.22, v3.23 and 1 more | postgresql17 | 17.12-r0 | ALPINE-CVE-2026-116313 |
| Alpine | v3.23, v3.24 | postgresql18 | 18.7-r0 | ALPINE-CVE-2026-116313 |
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. 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.
This vulnerability is rated as Important because it allows a malicious database owner to achieve complete privilege escalation by executing arbitrary commands with the administrative privileges of the account running maintenance utilities. The risk arises during maintenance routines where untrusted user-defined operators can hijack internal catalog queries. Red Hat enterprise deployments are generally not exposed under default installations as supported platforms ship major versions of PostgreSQL that predate the introduction of the vulnerable catalog query behavior.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | libpq | Affected | |
| Red Hat Hardened Images | postgresql17 | Affected | |
| Red Hat Hardened Images | postgresql18 | Affected |
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-116313.
Attack patterns (CAPEC)
- CAPEC-38 Leveraging/Manipulating Configuration File Search Paths Likelihood: High · Severity: Very High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.