LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
10

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.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-1285: 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32286 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
5Timeline events
2ADP providers
24Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6CISA-ADP
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-32286Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPgithub.com/jackc/pgproto3/v2: github.com/jackc/pgproto3/v2: Denial of Service via malicious PostgreSQL server
other:Red Hat severity ratingcvssV3_1
  • 2026-03-26T20:01:59.226Z: Reported to Red Hat.
  • 2026-03-26T19:40:51.974Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
github.com/jackc/pgproto3/v2github.com/jackc/pgproto3/v2github.com/jackc/pgproto3/v2, 0affected
Weakness

CWE details

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.

CWE-1285 · source CWE mapping

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.