CVE-2026-116313: PostgreSQL · Untrusted Search Path
Affects PostgreSQLSource CVE Database V5
Not known to be exploited · CVSS 7.2 High : upgrade to 18.7 soon.
Data as of 12 Nov 2026, 14:49 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 7.2 |
|---|
- Patch
- Available – fixed in 18.7
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade PostgreSQL to 18.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
AI-suggested
Upgrade affected PostgreSQL installations to version 18.7 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated. Since this is a local privilege escalation via vacuumdb, restricting access to database owner roles and careful invocation of vacuumdb can reduce risk until patched.
Description
CVE-2026-116313 is a high-severity vulnerability in PostgreSQL versions 18.0 up to but not including 18.7. It involves an untrusted search path in the vacuumdb utility, which allows a database owner to execute arbitrary SQL commands as the database user running vacuumdb. This occurs via shadowing operators used in the --missing-stats-only catalog query. Versions prior to PostgreSQL 18 are not affected. The issue is fixed in PostgreSQL 18.7.