# CVE-2026-32286: Denial of service in github.com/jackc/pgproto3/v2

> A malicious PostgreSQL server can cause a client application panic by sending a DataRow message with a negative field length.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 10 Sep 2026
- **Also known as:** CLEANSTART-2026-LY29111, CLEANSTART-2026-PO98584, CVE-2026-4427, DEBIAN-CVE-2026-32286, GHSA-jqcq-xjh3-6g23, GO-2026-4518, MINI-2pm7-6c29-7xvq, MINI-2prj-qvxh-pmc6, MINI-35m7-jc6c-j4c8, MINI-422m-rmqr-xc5m, MINI-443f-qw43-386c, MINI-62cj-85fp-48r2, MINI-66vf-59rm-rpq7, MINI-6fwx-9pvh-73j3, MINI-6gc3-wph8-j2xh, MINI-77c4-8ghx-vg9j, MINI-7mg6-6qfp-fphx, MINI-9637-mp6c-88ww, MINI-9vmx-6rx2-8j66, MINI-c254-p7wx-5j7j, MINI-c363-hphw-q6hx, MINI-f42r-6v96-6hwr, MINI-fqx4-rwgx-q5mc, MINI-ghqf-h4wf-358p, MINI-ghvx-wm83-8234, MINI-j66v-xm6m-f7gm, MINI-mm87-4xv9-52f4, MINI-pxgr-qjfw-23xq, MINI-qh8h-rmmr-jg28, MINI-v9w2-x6q6-f2r6, MINI-vfvr-2fr8-gpxw, MINI-w4w5-p9gr-wfpp, MINI-wq3x-6jx7-xcrq, MINI-wvfw-m24w-vp93, MINI-wvvr-xcw4-gqrv, MINI-wxxr-3w2j-mf3g, ROOT-APP-GOBINARY-CVE-2026-32286, UBUNTU-CVE-2026-32286

## What is CVE-2026-32286?

CVE-2026-32286 is a high-severity denial of service vulnerability in github.com/jackc/pgproto3/v2, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-129 (Improper Validation of Array Index), CWE-1285 (Improper Validation of Specified Index, Position, or Offset in Input)

## Which versions are affected by CVE-2026-32286?

3 open source packages ship an affected version, including github.com/jackc/pgproto3/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/jackc/pgproto3/v2` | Go | From 2.0.0 | None |
| `github.com/jackc/pgproto3/v2` | Go | From 2.0.0 to 2.3.3 | None |
| `github.com/jackc/pgproto3/v2` | Go | From 2.0.0 to 2.3.3 | None |

Products: Jackc Pgproto3.

## How do I fix CVE-2026-32286?

Upgrade to a fixed version.

## Is CVE-2026-32286 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32286 exists.

Public exploit code:

- Fork of jfrog/go-dbmigrate with pgx/v5 upgrade (CVE-2026-32286) (github_poc): https://github.com/moisei-dev/go-dbmigrate
- SlashID fork of conductorone/baton-retool — pgx/v5 port (CVE-2026-32286, CVE-2026-41889); retire when upstream ships pgx/v5 (github_poc): https://github.com/slashid/baton-retool

## Other vulnerabilities in github.com/jackc/pgproto3/v2

- [CVE-2024-27304](https://insights.sbomify.com/CVE-2024-27304/): pgx SQL Injection via Protocol Message Size Overflow (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32286 and fix it if it is affected.

What it is: CVE-2026-32286 is a high-severity denial of service vulnerability in github.com/jackc/pgproto3/v2, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32286 exists.

Affected packages and fixed versions:
- github.com/jackc/pgproto3/v2 (Go): affected from 2.0.0; no fix listed
- github.com/jackc/pgproto3/v2 (Go): affected from 2.0.0 up to 2.3.3; no fix listed
- github.com/jackc/pgproto3/v2 (Go): affected from 2.0.0 up to 2.3.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32286/ (Markdown: https://insights.sbomify.com/CVE-2026-32286/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32286
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32286
- OSV: https://osv.dev/vulnerability/CVE-2026-32286

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32286/
Summaries are generated and may contain mistakes; the official description above is the record.