AI Science Tracker

PostgreSQL: PostgreSQL type confusion in cursor CLOSE + DECLARE executes arbitrary code

PostgreSQL · AI involvement attributed to The PostgreSQL project thanks Ben Morris (Claude and Anthropic Research) for reporting this problem.

Finding and attribution

Type confusion in PostgreSQL "portal"/cursor lifecycle allows a user to execute arbitrary code as the operating system user running the database, via re-creation of a cursor or other portal with different types. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

Product: PostgreSQL. AI system: The PostgreSQL project thanks Ben Morris (Claude and Anthropic Research) for reporting this problem.. Team / organization: PostgreSQL (CNA); AI attribution as credited in the CVE record.

CVE identifiers: CVE-2026-16239.

AI and human contribution (source account): The CNA record credits 'The PostgreSQL project thanks Ben Morris (Claude and Anthropic Research) for reporting this problem.'. It states the AI attribution as written there and does not describe the model's operation, autonomy or the human validation steps; none is inferred.

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 CNA record establishes a coordinated disclosure with the credit above. It does not establish exploitation in the wild or a zero-day incident.

Remediation status: not established. The CNA record states no fixed version, patch or solution; check the vendor advisory.

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 13 Aug 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: High · highest recorded score 8.8. Documented technical effects: Not available.

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.

Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.

Documented fix: The CNA record states no fixed version, patch or solution; check the vendor advisory.

Original evidence

Download this source record (JSON)

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