CVE-2026-32286: Denial of service in github.com/jackc/pgproto3/v2
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.
Security readout for executives and security teams
Plain-English summary
This flaw can crash Go applications that parse PostgreSQL responses with pgproto3/v2. A malicious or compromised PostgreSQL server can send a malformed DataRow message and trigger a panic, causing service interruption. The business impact is availability loss, especially for services that depend on PostgreSQL connectivity.
Executive priority
Treat as high priority for Go services that rely on PostgreSQL, especially customer-facing systems. The issue is availability-focused rather than data theft, but a crashable database client can still create meaningful outage risk.
Technical view
DataRow.Decode does not properly validate field lengths. A negative field length in a PostgreSQL wire-protocol DataRow can cause a slice bounds out of range panic. The CVSS 3.1 score is 7.5, reflecting network reachability, low complexity, no privileges, no user interaction, and high availability impact only.
Likely exposure
Exposure is most likely in Go services using github.com/jackc/pgproto3/v2 directly or through related PostgreSQL client stacks such as pgx. Risk is higher where applications connect to PostgreSQL servers not fully controlled or where server compromise is plausible.
Exploitation context
The bundle includes public research marked as exploit-related, but it does not show confirmed active exploitation. The CVE is not listed as KEV. The attack requires a malicious or compromised PostgreSQL server response path, not a normal unauthenticated web request to the application.
Researcher notes
The key condition is a negative field length in a DataRow message reaching DataRow.Decode. Sources do not provide complete fixed-version detail in the supplied bundle, so remediation should be anchored to upstream and vendor advisories rather than assumed versions.
Mitigation direction
Identify applications depending on github.com/jackc/pgproto3/v2.
Check upstream pgproto3, pgx, and Go vuln guidance for fixed versions.
Apply relevant Red Hat advisories where Red Hat packaged software is in use.
Restrict applications to trusted PostgreSQL servers and protected network paths.
Prioritize services where database unavailability affects customer-facing operations.
Validation and detection
Review Go module manifests and SBOMs for github.com/jackc/pgproto3/v2.
Check whether pgx or other libraries introduce pgproto3/v2 transitively.
Map affected services to PostgreSQL endpoints and trust boundaries.
Confirm whether vendor advisories apply to deployed Red Hat products.
Verify remediation by comparing dependency versions against vendor guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Validation of Specified Index, Position, or Offset in Input
Improper Validation of Specified Index, Position, or Offset in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.