CVE-2026-32286

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-18. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

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

A fix is available — apply it.

The DataRow.Decode function fails to properly validate field lengths. A malicious or compromised PostgreSQL server can send a DataRow message with a negative field length, causing a slice bounds out of range panic.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

March 26, 2026

Last Modified

August 24, 2026

Advisory Details (10)

Auto-updated Jul 3, 2026
Patch available. Sources: github, redhat.
generic

GO-2026-4518 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4518
generic

Negative field length panics in DataRow.Decode · Issue #2507 · jackc/pgx · GitHub

https://github.com/jackc/pgx/issues/2507
generic

x/vulndb: potential Go vuln in github.com/jackc/pgproto3 · Issue #4518 · golang/vulndb · GitHub

https://github.com/golang/vulndb/issues/4518
github Patch Available

Denial of service in github.com/jackc/pgproto3/v2 · CVE-2026-32286 · GitHub Advisory Database · GitHub

https://github.com/advisories/GHSA-jqcq-xjh3-6g23

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatquay/quay-rhel8:17808913952026-06-09redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17801671182026-06-04redhat
redhatosbuild-composer-0:165.1-2.el9_82026-06-03redhat
redhatosbuild-composer-0:165.1-2.el10_22026-06-02redhat
redhatmulticluster-globalhub/multicluster-globalhub-rhel9-operator:17792099922026-06-02redhat
redhatquay/quay-rhel9:17799222052026-06-02redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17795794392026-06-01redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17788677532026-05-28redhat
redhatquay/quay-rhel8:17796893922026-05-26redhat
redhatquay/quay-rhel9:17792040862026-05-19redhat
redhatquay/quay-rhel8:17767823692026-04-30redhat
redhatquay/quay-rhel8:17767369102026-04-29redhat
redhatquay/quay-rhel8:17767526462026-04-29redhat
redhatadvanced-cluster-security/rhacs-scanner-v4-rhel8:17773077912026-04-27redhat
gogithub.com/jackc/pgproto3/v2ghsa

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-github-jackc-pgproto32.2.0-2, 2.3.2-1, 2.3.3-1, 2.3.3-1~exp0, 2.3.3-2
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-github-jackc-pgproto32.3.2-1, 2.3.3-1, 2.3.3-1~exp0, 2.3.3-2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-github-jackc-pgproto32.3.2-1, 2.3.3-1, 2.3.3-1~exp02.3.3-2
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/jackc/pgproto3/v2

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 92× 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 252 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-32286?
CVE-2026-32286 is a high vulnerability published on March 26, 2026. The DataRow.Decode function fails to properly validate field lengths. A malicious or compromised PostgreSQL server can send a DataRow message with a negative field length, causing a slice bounds out of range panic.
When was CVE-2026-32286 disclosed?
CVE-2026-32286 was first published in the National Vulnerability Database on March 26, 2026, with the most recent update on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32286 actively exploited?
CVE-2026-32286 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 51.2% of all scored CVEs.
What is the CVSS score of CVE-2026-32286?
CVE-2026-32286 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-32286?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32286, 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-32286

Explore →

Is Your Infrastructure Affected by CVE-2026-32286?

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