Security Digest · Vulnerability record
CVE-2026-6460: PostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code
Type confusion in PostgreSQL allows an object creator to execute arbitrary code as the operating system user running the database, via ALTER ...
CVSS 8.8 High EPSS 0.6% · p51 Patch this week
Should you act?
Normal patch cycle
No exploitation signal; fix it in your next routine update if you are affected. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.6%, percentile 51: FIRST’s model estimates a 0.6% chance of exploitation activity in the next 30 days, higher than 51% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Needs an account (low (any account)). Exposure depends on who can log in.
- Editorial verdict: Patch this week. PostgreSQL Fixes 52 CVEs, Including CVE-2026-6460 RCE — An attacker needs a database login first, and no attacks have been reported, but crash code is public, 32 of the fixes are rated 8.8, and any role that can create objects can reach code execution, so update every server and client this week.
What it is
Type confusion in PostgreSQL allows an object creator to execute arbitrary code as the operating system user running the database, via ALTER ... SET DATA TYPE primarily. Other DDL attack routes exist, such as "ALTER TABLE ... ADD COLUMN; ROLLBACK; ALTER TABLE ... ADD COLUMN". The system had inadequate tracking of typed values, and values were not self-identifying. Stale values could appear in data dictionary entries, PL/pgSQL variables, and many other parts of the system. PostgreSQL Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
Weakness type: CWE-843.
Product: PostgreSQL · Assigned by: PostgreSQL · Published: 2026-11-12
Affected and fixed versions
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| n/a | PostgreSQL | 18 < 18.7, 17 < 17.12, 16 < 16.16, 15 < 15.20, < 14.25 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| PostgreSQL | 3.1 | 8.8 High | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: low (any account)
- User interaction: none
- Scope: unchanged
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable no, technical impact total.
- FIRST EPSS (model of 2026-11-21): 0.64% probability of exploitation activity in the next 30 days; percentile 51.
Timeline
- — CVE record published by PostgreSQL
- — erroneo.us brief: PostgreSQL Fixes 52 CVEs, Including CVE-2026-6460 RCE
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- CVE.org record CVE-2026-6460 cve.org
- NVD entry CVE-2026-6460 nvd.nist.gov
Other references from the CVE record and advisory
- postgresql.org postgresql.org