---
title: "CVE-2026-6460: PostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code"
url: https://erroneo.us/security/cve/CVE-2026-6460/
description: "CVE-2026-6460 (PostgreSQL): Type confusion in PostgreSQL allows an object creator to execute arbitrary code as the operating system user running the…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-11-12
date_modified: 2026-11-16
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-6460"
kev: false
cvss: 8.8
epss: 0.00635
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2026-6460: PostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code

**Signal:** Normal patch cycle. No exploitation signal; fix it in your next routine update if you are affected. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- 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.

## Affected products (CVE record)

- n/a PostgreSQL: 18 < 18.7, 17 < 17.12, 16 < 16.16, 15 < 15.20, < 14.25

## Severity

- PostgreSQL CVSS 3.1: 8.8 `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`

## Exploitation

- 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.

## Sources

- [CVE.org record CVE-2026-6460](https://www.cve.org/CVERecord?id=CVE-2026-6460)
- [NVD entry CVE-2026-6460](https://nvd.nist.gov/vuln/detail/CVE-2026-6460)
- [postgresql.org](https://www.postgresql.org/support/security/CVE-2026-6460/)

---
Source page: https://erroneo.us/security/cve/CVE-2026-6460/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt
