Skip to main content
CVE-2026-116329VulnerabilityPublished

PostgreSQL statistics import · Type Confusion

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-116329· High 8.8

Not known to be exploited · CVSS 8.8 High : upgrade to 18.7 soon.

Data as of 12 Nov 2026, 16:21 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
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 PostgreSQL and postgresql/postgresql to 18.7.

Affected software

ProductAffectedFixed in
PostgreSQLAffected
  • >=18 <18.7
Fixed in
  • 18.7
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threatsAffected
  • >=18 <18.7
Fixed in
  • 18.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in PostgreSQL version 18.7. Users running PostgreSQL 18 versions prior to 18.7 should upgrade to 18.7 or later to remediate this vulnerability. No other mitigation or temporary workaround is indicated in the provided data.

Description

A type confusion vulnerability in PostgreSQL statistics import allows a table maintainer to execute arbitrary code as the operating system user running the database. This occurs via nested SET DATA TYPE during conversion of values to import. The issue affects PostgreSQL major version 18 prior to minor version 18.7. Versions before PostgreSQL 18 are not affected.

References

Community reviews

Loading reviews…