PostgreSQL
PostgreSQL pgcrypto heap buffer overflow executes arbitrary code
Heap buffer overflow in PostgreSQL pgcrypto allows a ciphertext provider to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 18, < 18.2
- >= 17, < 17.8
- >= 16, < 16.12
- >= 15, < 15.16
- < 14.21
Fixed in 18.2, 17.8, 16.12, 15.16, 14.21
Mitigation
Upgrade PostgreSQL to 18.2 or 17.8 or 16.12 or 15.16 or 14.21 or later.
Timeline
Days relative to CVE publicationFirst public PoC 23 days after publication; not in CISA KEV. First PoC: M3str3/CVE-2026-2005 (created 7 Mar 2026, found by us: backfilled).
PoC repositories
Found on GitHub.3 PoCs · 1 pending · 1 suspicious or fake
PoCs 3
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| M3str3/CVE-2026-2005 | 7 Mar 2026 +23 d | 0 | PoC via PoC Index |
| var77/CVE-2026-2005 | 13 May 2026 +90 d | 27 | PoC |
| open-flaw/CVE-2026-2005 | 10 Aug 2026 +179 d | 0 | PoC |
Pending 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| stvm8/CVE-2026-2005_lab | 4 May 2026 +81 d | 0 | Pending
Flags · score 15
Below the suspicion threshold (50); does not change the assessment. |
Suspicious or fake 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| dinosn/cve-2026-2005 | 5 May 2026 +82 d | 18 | Fake |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.