20 Year old pgcrypto CVE reported
Recent vulnerabilities in the pgcrypto extension of PostgreSQL have been disclosed, specifically CVE-2026-2005 and CVE-2026-2006. Both issues, which allow for remote code execution, have existed since the extension's inception in 2005. Users are urged to patch their systems promptly to mitigate these risks, especially given the wide vulnerability surface due to default permissions.
- ▪CVE-2026-2005 is a heap overflow vulnerability that can lead to arbitrary writes on the backend heap.
- ▪CVE-2026-2006 is an encoding-validation bug that also allows for remote code execution.
- ▪The vulnerabilities were discovered through AI-assisted fuzzing during a December event.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Thebuild |
| Canonical URL | https://thebuild.com/blog/2026/05/15/two-decades-two-rces-what-pgcrypto-has-been-doing-since-2005/ |
| Publication time | Wed, 20 May 2026 01:50:33 +0000 |
| Retrieval time | 2026-05-20T02:04:58.856Z |
| Last seen | 2026-05-20T02:04:58.856Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | dqmy726E_8Ya |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
2026-05-15 3 min PostgreSQL Two Decades, Two RCEs: What pgcrypto Has Been Doing Since 2005 On May 4, ZeroDay.Cloud published the technical writeups for CVE-2026-2005 and CVE-2026-2006. Both are remote code execution bugs in pgcrypto. Both have been in the tree since pgcrypto was first contributed in 2005. That’s the headline. It deserves a beat to land. CVE-2026-2005 is a 32-byte heap overflow in pgp_parse_pubenc_sesskey(). The code decrypts an RSA or ElGamal session-key payload from a PGP message and copies the result into a fixed-size buffer (ctx->sess_key, bounded at 32 bytes) with no bounds check at all. Hand the function a PGP message with a larger session key and you get arbitrary writes onto the backend heap. The path to RCE inside the database process is mechanical from there.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Thebuild.
Discussion
0 commentsMore from Thebuild
