AI Science Tracker

PostgreSQL composite-type type confusion can execute code

PostgreSQL core server · AI involvement attributed to Claude

Finding and attribution

A database object creator can exploit stale or misidentified typed values after composite-type changes to trigger type confusion and execute arbitrary code as the operating-system user running PostgreSQL. The vendor describes ALTER ... SET DATA TYPE as a principal route, with other DDL sequences possible. Full protection requires the versioned composite-datum checks; C-language extensions may need rebuilding, and disabling composite_type_mismatch carries security risks.

Product: PostgreSQL core server. AI system: Claude. Team / organization: Anthropic / Ada Logics.

CVE identifiers: CVE-2026-6460.

AI and human contribution (source account): The PostgreSQL 18.7 release notes thank Claude and Ada Logics for reporting this CVE, among a broader group of additional named reporters and organizations including OpenAI Security Research Team and Anthropic OSS program. This is case-specific collaborative reporting credit, not proof that Claude autonomously found the issue or that it was the first report.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The PostgreSQL security page publicly discloses the issue with the coordinated release. The cited sources do not establish whether exploitation preceded disclosure.

Remediation status: fix documented. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. Fixed in those respective releases on 2026-11-12. The release notes state full composite-type protections may require rebuilding C-language extensions; that caveat applies to the composite-type defense family, not automatically every case. Fixed releases do not establish downstream deployment.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 12 Nov 2026. AI attribution dated 12 Nov 2026. Sources checked 16 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: High · highest recorded score 8.8. Documented technical effects: code execution.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

CVE-2026-6460: code execution.
Prerequisites / affected scope: Requires an attacker able to create database objects; code runs with the database server operating-system account..
Exploitation evidence: No in-the-wild exploitation claim in the cited PostgreSQL sources.. Impact source · checked 16 Nov 2026.

Documented fix: Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. Fixed in those respective releases on 2026-11-12. The release notes state full composite-type protections may require rebuilding C-language extensions; that caveat applies to the composite-type defense family, not automatically every case. Fixed releases do not establish downstream deployment.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases