# PostgreSQL: object creation privileges can lead to server code execution

Canonical: https://www.oktsec.com/radar/postgresql-ddl-cve-2026-6460
Publisher: Oktsec
Language: en
Published: 2026-11-17T13:34:30Z
Updated: 2026-11-17T13:34:30Z
Record reviewed: 2026-11-17T13:34:30Z
Latest evidence check: 2026-11-17T13:34:30Z
Disclosed: 2026-11-12

A database user permitted to create objects can trigger code execution as the operating system account running PostgreSQL through crafted DDL operations. The project has released corrections for branches 14 through 18.

## Evidence and response priority

- Category: Vulnerability
- Oktsec priority: Review this week
- Rationale: Object creation permissions are a prerequisite. Branch corrections are available; the reviewed project sources do not establish attacks.
- Evidence: Attacks not established
- Verification: Vendor confirmed
- Fix status: Fix available
- Exposure requirement: Application or configuration dependent
- Vendor: PostgreSQL
- Products: PostgreSQL
- CVEs: CVE-2026-6460

## Technical overview

The vulnerable path includes ALTER ... SET DATA TYPE and other DDL operations. Successful exploitation crosses the boundary between a database role and the operating system identity running the server. It is not evidence of root access.

PostgreSQL published the fixes on November 12. The advisory does not establish exploitation in production. Review object creation privileges alongside the update, particularly where applications share a database with less trusted users.

The release announcement also lists maintenance steps for certain indexes and backup configurations. Apply those only where relevant to the installed environment. PostgreSQL 19 RC 2 is a prerelease, not the recommended replacement for a supported production branch.

PostgreSQL 14.25 is the final release of branch 14. It fixes this issue but does not extend upstream support. Plan migration to a supported major version.

## Recommended response

Install the corrected minor release for your PostgreSQL branch, restart the server and verify its running version. Review which application accounts can create database objects.

Relevant to: Database administrators and teams operating PostgreSQL for applications or automation.

## CVE attribution

- CVE-2026-6460: PostgreSQL — PostgreSQL. [Source](https://www.postgresql.org/support/security/CVE-2026-6460/)

## Affected systems and fixes

### PostgreSQL 18

Affected: 18.x before 18.7. Exploitation requires permission to create database objects.

Fixed release / action: 18.7

### PostgreSQL 17

Affected: 17.x before 17.12. Exploitation requires permission to create database objects.

Fixed release / action: 17.12

### PostgreSQL 16

Affected: 16.x before 16.16. Exploitation requires permission to create database objects.

Fixed release / action: 16.16

### PostgreSQL 15

Affected: 15.x before 15.20. Exploitation requires permission to create database objects.

Fixed release / action: 15.20

### PostgreSQL 14

Affected: 14.x before 14.25. Exploitation requires permission to create database objects. PostgreSQL 14 is now outside upstream support.

Fixed release / action: 14.25

Confirm the running version against the vendor advisory, including any distribution backports.

## CISA KEV evidence

Catalog: 2026.11.17
Checked: 2026-11-17T19:15:14.934Z

No matching CVE appears in the reviewed catalog snapshot.

CISA KEV inclusion establishes known exploitation of the listed CVE, not compromise of your environment. Absence does not rule out exploitation. The date added is not the first attack date. Federal deadlines and forensic triage requirements are context, not universal obligations for private organizations or businesses in Latin America.

## Supporting evidence

Snapshot checked: 2026-11-17T19:15:16.057Z. These dates do not change the incident’s editorial review date.

### FIRST EPSS forecast

- [CVE-2026-6460](https://api.first.org/data/v1/epss?cve=CVE-2026-6460): 0.59% probability of observed exploitation in the next 30 days; percentile 48.84%; score date 2026-11-17.

EPSS is a prediction, not exploitation evidence or organization-specific risk. Confirmed exploitation takes precedence. A missing score is not zero. Check status: available; last successful check: 2026-11-17T19:15:16.057Z.

### Official regional advisories

- [Vulnerabilidad en PostgreSQL](https://www.cert.gov.py/vulnerabilidad-en-postgresql-2/) — CERT-PY, Paraguay; publication 2026-11-16T11:27:42.000Z; observed 2026-11-17T19:15:16.057Z; matched by exact CVE identifier.

Publisher country does not establish victim location. Original notices may repeat the same underlying advisory.

## Response checklist

1. **Identify versions and privileges** — Inventory running PostgreSQL instances and accounts that can create objects. A network connection alone does not satisfy the reported prerequisite.
2. **Apply the branch correction** — Stop the server, update its binaries to the corrected minor release and restart. A minor update does not require pg_upgrade or a dump and reload; review the release notes for additional steps applicable to your installation.
3. **Check the running service** — Oktsec recommends checking the version reported by each restarted instance and testing application connections. Restrict unnecessary object creation permissions.
4. **Plan migration from PostgreSQL 14** — 14.25 is the final PostgreSQL 14 release. Apply its correction if still on that branch and plan migration to a supported major version.

## Relevance to AI environments

Check the DDL permissions assigned to application and agent database accounts.

## Sources

- [CVE-2026-6460: DDL code execution and corrected branches](https://www.postgresql.org/support/security/CVE-2026-6460/) — PostgreSQL; Vendor notice; checked 2026-11-17T13:34:30Z
- [November 12 minor releases and update instructions](https://www.postgresql.org/about/news/postgresql-187-1712-1616-1520-1425-and-19-rc-2-released-3442/) — PostgreSQL; Vendor notice; checked 2026-11-17T13:34:30Z

## Editorial record

- 2026-11-17T13:34:30Z: Added verified scope, branch corrections and installation guidance from primary sources.

## Use this advisory in Radar

Use the Advisory view to understand the issue and its evidence, Affected systems to compare versions, and Response plan to record applicability, an owner and action progress. Plans are saved only in the current browser and can be downloaded for sharing; they are not a shared team account or an automated scan. Completing a plan does not validate remediation. Talk to Oktsec opens a technical consultation with the advisory and selected service preserved. Scope, fees and access are agreed before any assessment.

[Open advisory](https://www.oktsec.com/radar/postgresql-ddl-cve-2026-6460) · [Build a response plan](https://www.oktsec.com/radar/postgresql-ddl-cve-2026-6460#review-workspace)

- [Exposure check consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=postgresql-ddl-cve-2026-6460&service=exposure_check)
- [Patch verification consultation](https://www.oktsec.com/contact?source=radar&intent=assessment&item=postgresql-ddl-cve-2026-6460&service=patch_verification)

## Scope and corrections

Radar is a selected editorial collection, not a complete vulnerability database or a scan of your environment. Priorities are Oktsec analysis. Source confirmation and checklist completion do not establish whether your systems are compromised or secure.

[Sources and methodology](https://www.oktsec.com/radar/about). Report corrections with supporting sources to info@oktsec.com. Do not send secrets or private incident data.

