Skip to main content
VulnerabilityPublished

CVE-2026-116316: PostgreSQL · Improper Protection of Alternate Path

Affects PostgreSQLSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High · fixed in 18.7 : patch PostgreSQL soon.

Data as of 12 Nov 2026, 14:49 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (PostgreSQL)CVSS 3.18.8
Patch
Available – fixed in 18.7, 17.12, 16.16 +2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
PostgreSQLAffected
  • >=18 <18.7
Fixed in
  • 18.7
PostgreSQLAffected
  • >=17 <17.12
Fixed in
  • 17.12
PostgreSQLAffected
  • >=16 <16.16
Fixed in
  • 16.16
PostgreSQLAffected
  • >=15 <15.20
Fixed in
  • 15.20
PostgreSQLAffected
  • <14.25
Fixed in
  • 14.25

AI-suggested

Upgrading PostgreSQL to versions 18.7, 17.12, 16.16, 15.20, or 14.25 or later fully mitigates this vulnerability. No other mitigation or workaround is indicated. Users should apply these official fixes promptly to prevent exploitation.

Description

CVE-2026-116316 is a vulnerability in PostgreSQL where improper protection of alternate paths in security-restricted operations allows an object creator to execute arbitrary SQL as the operation's caller. This occurs via domain, enum, or range types created in the temporary schema pg_temp. The vulnerability affects versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25. The attack requires the victim session to run a query with an unqualified type name, which common security-restricted operations like autovacuum do not do, so they are not affected.

References

Community reviews

Loading reviews…