Skip to main content
CVE-2026-116303VulnerabilityPublished

PostgreSQL type conversion · Missing Authorization

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-116303· Low 3.1

Not known to be exploited · CVSS 3.1 Low · fixed in 18.7 : update PostgreSQL when convenient.

Data as of 12 Nov 2026, 16:35 UTC

CVSS 3.1 base score
3.1Low
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.13.1
Patch
Available – fixed in 18.7, 17.12, 16.16 +2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

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
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threatsAffected
  • <14.25
  • <15.20
  • <16.16
  • <17.12
  • <18.7
Fixed in
  • 14.25
  • 15.20
  • 16.16
  • 17.12
  • 18.7

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

AI-suggested

Since affected versions are explicitly listed, upgrading PostgreSQL to versions 18.7, 17.12, 16.16, 15.20, or 14.25 and later will remediate the vulnerability. Until then, restrict database user privileges carefully and monitor for unusual access patterns. Patch status is not explicitly confirmed in the input; users should consult official PostgreSQL advisories for current remediation guidance.

Description

A missing authorization check in PostgreSQL type conversion allows database users to invoke cast functions without having EXECUTE privilege on those functions. This can occur via mechanisms such as foreign keys and the to_json() function. Exploitation requires an attacker to identify access-restricted cast functions and assess confidentiality impact, which is reportedly rare or minimal. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. The vulnerability has a low CVSS score and no known exploits in the wild.

References

Community reviews

Loading reviews…