CVE-2026-6460
PostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code
No known exploitation. EPSS puts it in the 49th percentile. Fixed versions are out.
No public exploit knownFix1 product4 fixed builds listed below
e.g. OID 1.3.6.1.4.1.25623.1.0.181050
What to do
Find your product and version, then upgrade to the build on the right.
- n/a PostgreSQLAffected: ≥ 18, < 18.7Upgrade to: 18.7Affected: ≥ 17, < 17.12Upgrade to: 17.12Affected: ≥ 16, < 16.16Upgrade to: 16.16Affected: ≥ 15, < 15.20Upgrade to: 15.20 + 1 more branchStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
Steps
Written by AI from the record- Check your PostgreSQL version by running
SELECT version();or asking whoever manages your database. - Confirm whether the version is older than 18.7, 17.12, 16.16, 15.20, or 14.25 (depending on which major branch you run).
- Schedule an upgrade to the fixed version for your branch (18.7, 17.12, 16.16, 15.20, or 14.25).
- Until upgraded, limit which database users are allowed to create or alter tables, since the attack requires that privilege.
- Ask your hosting provider or IT team if they manage PostgreSQL updates automatically, and confirm the patch has been applied.
What it is
From the CVE record
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.
In plain language
Written by AI from the recordA flaw in PostgreSQL databases lets someone who can already create objects in the database run commands as the database's operating system user — PostgreSQL has fixed it, and businesses running their own PostgreSQL databases should update soon.
Type confusion in PostgreSQL's handling of DDL (notably ALTER ... SET DATA TYPE and ADD COLUMN/ROLLBACK sequences) allows a user with object-creation privilege to cause stale, non-self-identifying typed values to be misinterpreted elsewhere in the system, resulting in arbitrary code execution as the OS user running the database.
If you're affected
- Full database server takeover
- Customer data exposure
- Operational disruption
- Privilege escalation from low-level DB user
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.6% chance of exploitation activity in the next 30 days, which ranks it in the 49th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
8 events over 3 days, from the signal feeds we watch.
- OpenVAS check added
- Record updated
- Publishedweakness classified, att&ck mapped, record updated, record updated, record updated
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Scored 8.8 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required LowRequires basic user-level privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Initial AccessT1190Exploit Public-Facing Applicationhigh confidence
- Privilege EscalationT1068Exploitation for Privilege Escalationhigh confidence
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI