CVE-2026-6460: PostgreSQL · Type Confusion
Source GCVE Database
Not known to be exploited · CVSS 8.8 High · fixed in 18.7 : patch PostgreSQL soon.
Data as of 12 Nov 2026, 16:20 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 8.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: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 to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability affects PostgreSQL versions prior to 18.7, 17.12, 16.16, 15.20, and 14.25. Users should upgrade to these fixed versions or later to remediate the issue. No vendor advisory or patch links were provided, but the presence of fixed versions indicates that official fixes exist in these releases. Applying these updates is the recommended mitigation.
Description
A type confusion vulnerability in PostgreSQL allows an object creator to execute arbitrary code with the privileges of the operating system user running the database. This occurs due to inadequate tracking of typed values, leading to stale values appearing in various system components. The flaw can be exploited primarily via ALTER ... SET DATA TYPE commands and other DDL operations. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. The vulnerability has a high severity score of 8.8 CVSS v3.1.