Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The github.com/jackc/pgproto3/v2 package, versions 2.0.0 through 2.3.3, is affected. The DataRow.Decode function does not properly validate field lengths, so a malicious or compromised PostgreSQL server that sends a DataRow message with a negative field length can cause a slice bounds out of range panic. No fixed version is listed.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0067, the 52nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:13 UTC First seen by agentprime
- 31 Oct 2026, 14:13 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-jqcq-xjh3-6g23
- OSV: GHSA-jqcq-xjh3-6g23
- nvd.nist.gov/vuln/detail/CVE-2026-32286
- github.com/golang/vulndb/issues/4518
- github.com/jackc/pgx/issues/2507
- bugzilla.redhat.com/show_bug.cgi?id=2448626
- github.com/jackc/pgproto3
- pkg.go.dev/vuln/GO-2026-4518
- securityinfinity.com/research/memory-safety-vulnerabilities-in-go-postgresql-wire-protocol-parsers-pgproto3-pgx