vulns.co
/
GKData.io MCP and API Buy me a coffee

PostgreSQL · Memory safety and parser contracts

PostgreSQL extension estimator trusted an unchecked input type

PostgreSQL's intarray extension did not check that input had the type its native code expected. The vendor confirms possible code execution as the database's operating-system account, requiring permission to install the extension or an existing installation plus object-creation permission. Wiz confirms a USD 30,000 award for Daniel Firer's competition entry and maps it to CVE-2026-2004.

Read the original writeupUSD 30,000 competition award · Reviewed 2026-10-02

Root cause

The extension’s selectivity estimator did not check that input had the type it expected. Native extension code running with database-process privileges then relied on that unchecked type. This broke the contract between objects an authorized database user could create and the extension code that handled them.

Demonstrated impact

The vendor confirms possible code execution as the database operating-system account. A user needed permission to install the vulnerable extension, or an existing installation plus object-creation permission. The public sources do not establish a universal unauthenticated or cross-tenant compromise.

What to check for

  • Validate input types at extension boundaries before applying native-code assumptions.
  • Review extension installation and object-creation privileges together; either permission in isolation can hide the relevant trust boundary.
  • Verify the vendor’s fixed releases and keep the database process identity limited to necessary resources.

Award and evidence

USD 30,000Competition Award · Organizer Confirmed
How the award was verified, and what the record does not establish

One individually identified competition entry. The organizer uses $; its current rules establish US-dollar notation but concern 2026, not an archived 2025 rules snapshot. Exact award decision and cash settlement are unknown.

  • The technical basis is the vendor advisory, not a detailed researcher walkthrough; discovery reasoning beyond that evidence is unknown.
  • The December competition demonstration, February advisory publication, award announcement and unknown payment date are distinct events.
  • Current rules provide explicit USD context but are not the archived 2025 rules.

Timeline

Published
2026-02-12explicit · Publication of the vendor CNA record; no separate detailed researcher article was established.
Public Disclosure
2025-12-10explicit · Public competition demonstration; separate from later vendor advisory and technical publication.
Fixed
2026-02-12explicit · Vendor release date for PostgreSQL 18.2, 17.8, 16.12, 15.16 and 14.21; individual deployment dates remain unknown.
Award Announced
2025-12-16explicit · Organizer recap confirms the per-entry award; decision and payment dates remain unknown.

Related cases

All 10 cases in Memory safety and parser contracts

Sources

  1. ZeroDay.cloud 2025 individual competition resultsNir Ohfeld / Wiz Research · reviewed 2026-10-02
  2. ZeroDay.cloud vulnerability trackerWiz / ZeroDay.cloud · reviewed 2026-10-02
  3. ZeroDay.cloud current rules: US-dollar denominationWiz · reviewed 2026-10-02
  4. PostgreSQL CVE-2026-2004 security advisoryPostgreSQL · reviewed 2026-10-02
  5. CVE-2026-2004 PostgreSQL CNA recordPostgreSQL CNA / CVE Program · reviewed 2026-10-02

Record reviewed 2026-10-02. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software