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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 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)
EPSS
39.1%
KEV
Not listed

Published

March 26, 2026

Last Modified

July 15, 2026

Advisory Details (10)

Auto-updated Jul 3, 2026
Patch available. Sources: github, redhat.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:19375
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:11996
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:11916
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:11856
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:11217
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:11070
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

Vendor Advisories for CVE-2026-32286(15)

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

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
redhatmulticluster-globalhub/multicluster-globalhub-rhel9-operator:17792099922026-06-02redhat
redhatquay/quay-rhel9:17799222052026-06-02redhat
redhatosbuild-composer-0:165.1-2.el10_22026-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/v2—ghsa

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

(1 across 1 ecosystem)
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 10× in last 7d / 42× 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 117 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 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-32286 actively exploited?
CVE-2026-32286 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.

Start Free Scan →Browse All CVEs