CVE-2026-2005

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-02-12. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
70%
KEV
Not listed

Published

February 12, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated Jun 7, 2026
No patch confirmed yet.
generic

PostgreSQL: CVE-2026-2005: PostgreSQL pgcrypto heap buffer overflow executes arbitrary code

https://www.postgresql.org/support/security/CVE-2026-2005/

Vendor Advisories for CVE-2026-2005(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpostgresql16-0:16.13-1.el10_22026-05-19redhat
redhatpostgresql18-0:18.3-1.el10_22026-05-19redhat
redhatpostgresql18-main-18.3-1.2.hum12026-04-17redhat
redhatrhui5/rhua-rhel9:17736701372026-03-18redhat
redhatpostgresql:12-8060020260306113941.ad008a3a2026-03-12redhat
redhatpostgresql:12-8020020260309120440.4cda2c842026-03-12redhat
redhatpostgresql-0:13.23-1.el9_4.12026-03-12redhat
redhatpostgresql:16-9040020260306102041.rhel92026-03-12redhat
redhatpostgresql:13-8060020260309111524.ad008a3a2026-03-12redhat
redhatpostgresql:16-9060020260305153549.rhel92026-03-12redhat
redhatpostgresql-0:13.23-1.el9_0.12026-03-12redhat
redhatpostgresql16-0:16.13-1.el10_02026-03-12redhat
redhatpostgresql:13-8040020260305144728.522a0ee42026-03-12redhat
redhatpostgresql-0:13.23-1.el9_6.12026-03-12redhat
redhatpostgresql-0:13.23-1.el9_2.12026-03-12redhat
redhatpostgresql:12-8040020260306101701.522a0ee42026-03-12redhat
redhatpostgresql:15-8080020260306092921.63b345852026-03-12redhat
redhatpostgresql:15-9040020260305163703.rhel92026-03-12redhat
redhatpostgresql:15-9060020260309125703.rhel92026-03-12redhat
redhatpostgresql:15-9020020260309133405.rhel92026-03-11redhat
redhatpostgresql:15-8100020260227221316.489197e62026-03-09redhat
redhatpostgresql:16-9070020260227095951.rhel92026-03-09redhat
redhatpostgresql:13-8080020260302123717.63b345852026-03-09redhat
redhatpostgresql:13-8100020260227180702.489197e62026-03-09redhat
redhatpostgresql:12-8080020260302123049.63b345852026-03-09redhat
redhatpostgresql:16-8100020260227221401.489197e62026-03-09redhat
redhatpostgresql:12-8100020260302082007.489197e62026-03-09redhat
redhatpostgresql:15-9070020260227094950.rhel92026-03-05redhat
redhatpostgresql16-0:16.13-1.el10_12026-03-05redhat
redhatpostgresql-0:13.23-2.el9_72026-03-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(14 across 9 ecosystems)
Alpine:v3.20(2)
PackageVulnerable rangeFixed inDependents
postgresql15—15.16-r0—
postgresql16—16.12-r0—
Alpine:v3.21(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.12-r0—
postgresql17—17.8-r0—
Alpine:v3.22(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.12-r0—
postgresql17—17.8-r0—
Alpine:v3.23(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.8-r0—
postgresql18—18.2-r0—
Alpine:v3.24(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.8-r0—
postgresql18—18.2-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
postgresql-1313.10-0+deb11u1 ... 13.9-0+deb11u1 (23 versions)13.23-0+deb11u2—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
postgresql-1515.10-0+deb12u1 ... 15.9-0+deb12u1 (18 versions)15.16-0+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
postgresql-1717.5-1, 17.6-0+deb13u1, 17.6-1, 17.7-0+deb13u117.8-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
postgresql-1818.0-1 ... 18~~devel.20250502-1 (17 versions)18.2-1—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(11)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 188 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-08-31 19:04 UTCOSV refresh
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-24 14:17 UTCEPSS rescore
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 22:36 UTCVendor advisory
  13. 2026-08-14 22:36 UTCGHSA enrichment
  14. 2026-08-14 10:14 UTCEG score recompute
  15. 2026-08-14 10:14 UTCVendor advisory
  16. 2026-08-14 10:14 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 02:31 UTCEG score recompute
  19. 2026-08-13 02:31 UTCVendor advisory
  20. 2026-08-13 02:31 UTCGHSA enrichment
  21. 2026-08-12 13:50 UTCEPSS rescore
  22. 2026-08-11 13:42 UTCEPSS rescore
  23. 2026-08-11 08:57 UTCEG score recompute
  24. 2026-08-11 08:57 UTCVendor advisory
  25. 2026-08-11 08:57 UTCGHSA enrichment
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 02:56 UTCVendor advisory
  28. 2026-08-10 02:56 UTCGHSA enrichment
  29. 2026-08-09 14:54 UTCEG score recompute
  30. 2026-08-09 14:54 UTCVendor advisory
  31. 2026-08-09 14:54 UTCGHSA enrichment
  32. 2026-08-09 13:46 UTCEPSS rescore
  33. 2026-08-08 16:37 UTCEPSS rescore
  34. 2026-08-08 09:50 UTCVendor advisory
  35. 2026-08-08 09:50 UTCGHSA enrichment
  36. 2026-08-07 22:04 UTCEG score recompute
  37. 2026-08-07 22:04 UTCVendor advisory
  38. 2026-08-07 22:04 UTCGHSA enrichment
  39. 2026-08-06 13:46 UTCEPSS rescore
  40. 2026-08-06 03:56 UTCEG score recompute
  41. 2026-08-06 03:56 UTCVendor advisory
  42. 2026-08-06 03:56 UTCGHSA enrichment
  43. 2026-08-05 19:17 UTCEPSS rescore
  44. 2026-08-04 15:10 UTCEPSS rescore
  45. 2026-08-03 10:36 UTCEPSS rescore
  46. 2026-08-02 20:44 UTCEG score recompute
  47. 2026-08-02 20:44 UTCVendor advisory
  48. 2026-08-02 20:44 UTCGHSA enrichment
  49. 2026-08-02 02:26 UTCEPSS rescore
  50. 2026-08-01 04:16 UTCEPSS rescore
  51. 2026-07-30 16:27 UTCEPSS rescore
  52. 2026-07-30 01:30 UTCEPSS rescore
  53. 2026-07-28 15:36 UTCEPSS rescore
  54. 2026-07-26 14:54 UTCEPSS rescore
  55. 2026-07-26 14:54 UTCEPSS rescore
  56. 2026-07-25 14:18 UTCEPSS rescore
  57. 2026-07-25 14:17 UTCEPSS rescore
  58. 2026-07-23 14:18 UTCEPSS rescore
  59. 2026-07-23 14:18 UTCEPSS rescore
  60. 2026-07-23 03:06 UTCEG score recompute
  61. 2026-07-22 14:08 UTCEPSS rescore
  62. 2026-07-22 14:08 UTCEPSS rescore
  63. 2026-07-21 15:24 UTCEPSS rescore
  64. 2026-07-21 15:24 UTCEPSS rescore
  65. 2026-07-20 17:08 UTCEPSS rescore
  66. 2026-07-20 17:08 UTCEPSS rescore
  67. 2026-07-19 14:31 UTCEPSS rescore
  68. 2026-07-19 14:31 UTCEPSS rescore
  69. 2026-07-19 02:29 UTCEPSS rescore
  70. 2026-07-18 10:04 UTCEPSS rescore
  71. 2026-07-18 10:04 UTCEPSS rescore
  72. 2026-07-17 14:59 UTCOSV refresh
  73. 2026-07-16 17:03 UTCEPSS rescore
  74. 2026-07-16 17:03 UTCEPSS rescore
  75. 2026-07-15 16:57 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCvar77/CVE-2026-2005
    First seen May 13, 2026

    PoC for CVE-2026-2005

    Open source ↗
  • GitHub PoCdinosn/cve-2026-2005
    First seen May 5, 2026

    CVE-2026-2005 — PostgreSQL pgcrypto heap overflow RCE exploit

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-2005?
CVE-2026-2005 is a high vulnerability published on February 12, 2026. 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.
When was CVE-2026-2005 disclosed?
CVE-2026-2005 was first published in the National Vulnerability Database on February 12, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2005 actively exploited?
CVE-2026-2005 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 30.4% of all scored CVEs.
What is the CVSS score of CVE-2026-2005?
CVE-2026-2005 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-2005?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2005, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-2005

Explore →

Is Your Infrastructure Affected by CVE-2026-2005?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs