Cyber Resilience

CVE-2026-32286

Jackc Pgproto3 2.0.0 – 2.3.3

Published
26 March 2026
Modified
12 August 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0065 48th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2026-32286 is a high-severity Improper Validation of Array Index (CWE-129) vulnerability in Jackc Pgproto3. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 48th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-32286 affects the DataRow.Decode function in Go-based PostgreSQL client libraries, such as pgx and pgproto3, which parse the PostgreSQL wire protocol. The vulnerability arises from improper validation of field lengths, allowing a malicious or compromised PostgreSQL server to send a DataRow message with a negative field length. This triggers a slice bounds out of range panic in the client application. Published on 2026-03-26, it has a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating high availability impact.

Any remote unauthenticated attacker with network access who controls or compromises a PostgreSQL server can exploit this vulnerability. By crafting and sending a DataRow message with a negative field length during a client connection, the attacker causes an immediate panic in the vulnerable client library. This results in denial of service, as the client process crashes without impacting confidentiality or integrity.

Advisories detail mitigations in GHSA-jqcq-xjh3-6g23, golang/vulndb issue #4518, jackc/pgx issue #2507, and pkg.go.dev/vuln/GO-2026-4518. Security practitioners should update to patched versions of affected libraries like pgx. Further analysis of memory safety issues in Go PostgreSQL wire protocol parsers appears in securityinfinity.com/research/memory-safety-vulnerabilities-in-go-postgresql-wire-protocol-parsers-pgproto3-pgx.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-129CWE-1285

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-27304Same product: Jackc Pgproto3
CVE-2026-33815Same vendor: Jackc
CVE-2026-33816Same vendor: Jackc
CVE-2025-3357Shared CWE-1285, CWE-129
CVE-2026-2006Shared CWE-1285, CWE-129
CVE-2026-32285Shared CWE-1285, CWE-129
CVE-2026-40886Shared CWE-1285, CWE-129
CVE-2026-41889Same vendor: Jackc
CVE-2024-27289Same vendor: Jackc
CVE-2023-31309Shared CWE-129

Affected Assets

jackc
pgproto3
2.0.0 — 2.3.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.4.2
  • V2.1.1
  • V2.2.1
  • V2.2.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Requires explicit validation of supplied indices/offsets/positions before they are used to access buffers or other indexable resources.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and bounds checking that prevent improper array indexing.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover missing index validation via scanning or reviews.

PR.PS-02 partial match
prevents

Patching and replacement can remediate instances of the weakness after discovery.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect out-of-bounds array access but does not prevent the weakness by itself.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and bounds checking that directly prevents improper array indexing.

A.8.26 Application security requirements partial match
prevents

Application security requirements include validation of untrusted input used for indexing or addressing memory structures.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles encourage defensive coding patterns that reduce index-related vulnerabilities.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require bounds checking and validation of array indices derived from untrusted data.

References