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
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
- Redis replication state changes invalidated an active interpreter
Redis · Memory safety and parser contracts · USD 30,000
- Redis deserialization cleanup violated object-ownership invariants
Redis · Memory safety and parser contracts · USD 30,000
- PostgreSQL cryptographic parsing omitted a buffer-capacity check
PostgreSQL · Memory safety and parser contracts · USD 30,000
- PostgreSQL text-encoding invariant failure caused memory corruption
PostgreSQL · Memory safety and parser contracts · USD 30,000
Sources
- ZeroDay.cloud 2025 individual competition resultsNir Ohfeld / Wiz Research · reviewed 2026-10-02
- ZeroDay.cloud vulnerability trackerWiz / ZeroDay.cloud · reviewed 2026-10-02
- ZeroDay.cloud current rules: US-dollar denominationWiz · reviewed 2026-10-02
- PostgreSQL CVE-2026-2004 security advisoryPostgreSQL · reviewed 2026-10-02
- 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.