CyberSecBulletin
CVE-2026-32286NVD status: Modified

github.com/jackc/pgproto3/v2: Improper Validation of Array Index

Published Updated By the CyberSecBulletin desk

CVE-2026-32286 is a high-severity improper validation of array index vulnerability in github.com/jackc/pgproto3/v2, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.69% chance of exploitation within 30 days, higher than 53% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of github.com/jackc/pgproto3/v2 you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on github.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Github.com/jackc/pgproto3/v2github.com/jackc/pgproto3/v2Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatMulticluster Global Hub 1.3.4Not specified in the recordNot stated
Red HatMulticluster Global Hub 1.4.5Not specified in the recordNot stated
Red HatMulticluster Global Hub 1.6.5Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Security 4.8Not specified in the recordNot stated
Red HatRed Hat multicluster global hub 1.5.3Not specified in the recordNot stated
Red HatRed Hat Quay 3.10Not specified in the recordNot stated
Red HatRed Hat Quay 3.12Not specified in the recordNot stated
Red HatRed Hat Quay 3.14Not specified in the recordNot stated
Red HatRed Hat Quay 3.15Not specified in the recordNot stated
Red HatRed Hat Quay 3.16Not specified in the recordNot stated
Red HatRed Hat Quay 3.17Not specified in the recordNot stated
Red HatRed Hat Quay 3.9Not specified in the recordNot stated
Red HatAssisted Installer for Red Hat OpenShift Container Platform 2Not specified in the recordNot stated
Red HatMulticluster Engine for KubernetesNot specified in the recordNot stated
Red HatMulticluster Global HubNot specified in the recordNot stated
Red HatRed Hat Advanced Cluster Management for Kubernetes 2Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Security 4Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Hardened ImagesNot specified in the recordNot stated
Red HatRed Hat OpenShift AI (RHOAI)Not specified in the recordNot stated
Red HatRed Hat OpenShift Cluster Manager CLINot specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE; 4 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

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

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighCISA (ADP)
CVSS 3.17.5HighCNA

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Validation of Array Index

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

How developers prevent this class of flaw

  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, Ada allows the programmer to constrain the values of a variable and languages such as Java and Ruby will allow the programmer to handle exceptions when an out-of-bounds index is accessed.
  • Use a CPU and operating system that offers Data Execution Protection (using hardware NX or XD bits) or the equivalent techniques that simulate this feature in software, such as PaX. These techniques ensure that any instruction executed is exclusively at a memory address that is part of the code segment. For more information on these techniques see D3-PSEP (Process Segment Execution Prevention) from D3FEND.

More Improper Validation of Array Index vulnerabilities (CWE-129)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Advisories

Recent Improper Validation of Array Index vulnerabilities

Spotted an error? Tell us.