AI description
CVE-2026-6460 is a type confusion vulnerability in the PostgreSQL core database engine that stems from inadequate tracking of typed values. Because stored values do not carry self-identifying type information, stale values can persist in data dictionary entries, PL/pgSQL variables, and other parts of the system. An authenticated user with object-creation privileges—which can include the default permission to create temporary objects—can trigger this flaw using Data Definition Language (DDL) commands, such as altering column data types (e.g., `ALTER ... SET DATA TYPE`). By manipulating these types, an attacker can execute arbitrary code on the host system with the privileges of the operating system user running the database service. The vulnerability, which security researcher Mehmet Ince traced back to a 22-year-old design choice in PostgreSQL's core, was patched on November 12, 2026. The PostgreSQL Global Development Group addressed the issue in versions 18.7, 17.12, 16.16, 15.20, and 14.25 by introducing version checks to ensure stored values match their expected types. To achieve full protection, administrators must not only update their database binaries but also rebuild any installed C-language extensions, as older compiled extensions may lack the necessary type-checking mechanisms.
- Description
- 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.
- Source
- f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
- NVD status
- Awaiting Analysis
CVSS 3.1
- Type
- Secondary
- Base score
- 8.8
- Impact score
- 5.9
- Exploitability score
- 2.8
- Vector string
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Severity
- HIGH
- f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
- CWE-843
Hype score is a measure of social media activity compared against trending CVEs from the past 12 months. Max score 100.
- Hype score
21
🚨 PUBLIC EXPLOIT OUT · PostgreSQL: 31 high-severity CVEs Worst (8.8): remote code execution in type handling during DDL (CVE-2026-6460) public exploit: CVE-2026-6460 👉 Fix: 5 fixes by release line, see page https://t.co/Vu3Dm4hDAd
@cvedotnow
14 Nov 2026
17549 Impressions
19 Retweets
159 Likes
103 Bookmarks
5 Replies
1 Quote
PostgreSQL 18.7/17.12/16.16/15.20/14.25 fix 52 CVEs. CVE-2026-6460 (CVSS 8.8) lets users who can create objects run code on the server. Patch, then rebuild C extensions. #PostgreSQL #CVE https://t.co/4XYqDoMoK7 https://t.co/FtC64o6ImF
@4tifysecurity
14 Nov 2026
14 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes
PostgreSQL CVE-2026-6460 and 51 more: are you affected and what to patch first PostgreSQL fixed 52 CVEs on 12 Nov 2026, incl. CVE-2026-6460 code execution. Fixed versions, how to check if you're affected, what to patch first… #cybersecurity #infosec https://t.co/BXiCMrt8Nh
@Gociux
14 Nov 2026
59 Impressions
0 Retweets
0 Likes
0 Bookmarks
2 Replies
0 Quotes
PostgreSQLの11月リリースでCVEが52件まとめて修正されてた。 攻撃成立するとやばめなのは ALTER ... SET DATA TYPE 後の型の取り違えでオブジェクトを作れる利用者が DB の OS ユーザー権限で任意コード実行できる脆弱
@burnworks
14 Nov 2026
97 Impressions
0 Retweets
0 Likes
0 Bookmarks
0 Replies
0 Quotes