Root cause
The trusted pgcrypto extension could return text that did not match the database's configured character encoding. Other text routines assumed that this validation had already happened and relied on it to calculate character lengths safely. The mismatch could corrupt memory. Defensive reviews should check that extensions and parsers enforce the encoding rules their callers rely on.
Demonstrated impact
Vendor confirms that an authenticated database user could reach code execution with the database operating-system account's privileges.
What to check for
- Validate encoding contracts at every trusted extension boundary.
- Avoid relying on unverified text invariants for memory-length calculations.
- Apply supported vendor fixes and retain regression coverage.
Award and evidence
How the award was verified, and what the record does not establish
One PostgreSQL competition-entry award to Team Bugz Bunnies, excluding the separate $10,000 Grafana award. The 2025 recap uses $ without explicitly naming a currency. USD is contextually inferred from the organizer's current rules (currency-context), which concern December 9-10, 2026 rather than an archived 2025 snapshot. That later context does not establish this individual award's denomination or cash settlement. No conversion is made; exact award and funds-transfer dates remain unknown.
- This is a per-finding competition award, not a traditional vendor bounty; keep award_type visible
- Do not count the team's $40,000 combined Grafana and PostgreSQL earnings as this finding's reward
- Actual funds-transfer date not published
- Current rules Section 4 supplies US-dollar context, but Section 2 dates the contest to December 9-10, 2026. This is not an archived 2025 rules snapshot or evidence of this individual award's denomination or cash settlement.
- The reviewed_at timestamp covers the initial 2026-10-02 review, not the currency-context supplement (ZeroDay.cloud current 2026 rules), retrieved at 2026-10-06T04:19:11Z and added to this record on October 6. The exact supplemental review time was not recorded. This metadata correction does not represent a new source review.
Timeline
- Reported
- 2025-12-11explicit
- Fixed
- 2026-02-12explicit
- Award Announced
- 2025-12-16explicit · Organizer recap announces the individual entry award; exact award/transfer date not published.
- Published
- 2026-05-04inferred · On-stage demonstration and vendor disclosure are explicitly December 11, 2025. Organizer payout recap was published December 16; cash transfer date is not stated. Detailed researcher article is dated May 4, with year contextualized by its 2026 fix timeline.
- Public Disclosure
- 2025-12-11explicit · Public competition demonstration; detailed technical publication followed in 2026.
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
- MariaDB JSON normalization exceeded allocated buffer capacity
MariaDB · Memory safety and parser contracts · USD 30,000
Sources
- PostgreSQL text-encoding invariant failure caused memory corruptionWiz / ZeroDay.cloud · reviewed 2026-10-02
- Supporting primary disclosure sourceWiz / ZeroDay.cloud · reviewed 2026-10-02
- Supporting primary disclosure sourcePaul Gerste, Moritz Sanft, Team Bugz Bunnies · reviewed 2026-10-02
- PostgreSQL CVE-2026-2006 vendor advisoryPostgreSQL Global Development Group · reviewed 2026-10-02
- ZeroDay.cloud current rules: US-dollar context for the 2026 contestWiz · reviewed 2026-10-06
Record reviewed 2026-10-02. Snapshot af2809c308fc. Open the complete JSON contract.