CVE-2026-96883: AWS pgcollection RCE Vulnerability

CVE-2026-96883 Overview

CVE-2026-96883 is a type confusion vulnerability [CWE-843] in the AWS pgcollection extension for PostgreSQL. The flaw affects versions 2.0.0 through 2.1.1 and stems from mismatched type metadata handled in collection value retrieval and array conversion functions. An authenticated remote database user can submit crafted SQL statements that trigger the mismatch and execute arbitrary code as the postgres operating system user. AWS published advisory 2026-118 and released a fixed build in pgcollection version 2.1.2.

Critical Impact

Authenticated database users can escape SQL context and run arbitrary code as the postgres OS user, compromising database confidentiality, integrity, and availability.

Affected Products

• AWS pgcollection 2.0.0
• AWS pgcollection 2.1.0
• AWS pgcollection 2.1.1

Discovery Timeline

• 2026-09-24 - CVE-2026-96883 published to the National Vulnerability Database
• 2026-09-25 - Last updated in NVD database

Technical Details for CVE-2026-96883

Vulnerability Analysis

The pgcollection extension adds collection data types to PostgreSQL. Internally, it stores typed values and exposes helper routines that retrieve collection elements and convert collections to arrays. The affected code paths trust type metadata recorded during insertion when later interpreting the stored value.

When the recorded type metadata does not match the actual value layout, the extension operates on memory under incorrect assumptions. This is a classic type confusion condition [CWE-843]. The result is attacker-controlled interpretation of memory inside the PostgreSQL backend process.

Because PostgreSQL backend processes run as the postgres operating system user, successful exploitation yields code execution with that identity. An attacker can read database files directly, modify catalog data, or pivot to other services the account can reach.

Root Cause

The root cause is inconsistent handling of type metadata between the write path and the read path of collection values. The collection value retrieval function and the array conversion function do not re-validate that the stored element type matches the type expected by the caller. Crafted SQL that mixes types across these functions causes the extension to coerce bytes using incorrect type descriptors.

Attack Vector

Exploitation requires authenticated access to a PostgreSQL database that loads the vulnerable pgcollection extension. The attacker issues SQL statements that build a collection with one declared element type and then invoke retrieval or array conversion functions that assume a different type. The mismatched descriptors drive memory interpretation errors that the attacker shapes into arbitrary code execution inside the backend process. No user interaction is required and the attack originates over the network through the normal PostgreSQL wire protocol.

No public proof-of-concept code is referenced in the AWS advisory or the GitHub Security Advisory GHSA-g539-cj32-hv6r. Technical details are described in prose in the AWS Security Bulletin 2026-118.

Detection Methods for CVE-2026-96883

Indicators of Compromise

• PostgreSQL backend crashes or SIGSEGV entries in server logs correlated with sessions that call pgcollection functions.
• Unexpected child processes spawned from the postgres OS user, including shells, network utilities, or compilers.
• Outbound network connections initiated by the PostgreSQL process to addresses outside the normal application topology.
• New or modified files under the PostgreSQL data directory or postgres user home that cannot be tied to a maintenance window.

Detection Strategies

• Query pg_extension across all databases to inventory hosts where pgcollection is installed and identify versions below 2.1.2.
• Audit PostgreSQL logs for sessions that mix collection element types across pgcollection retrieval and array conversion functions in a single transaction.
• Monitor for process lineage anomalies where postgres is the parent of non-database binaries.

Monitoring Recommendations

• Enable log_min_messages = warning and log_statement = 'ddl' to capture extension loading and schema changes involving pgcollection.
• Forward PostgreSQL logs and host process telemetry to a centralized analytics platform for correlation across database and OS layers.
• Alert on any new role granted EXECUTE on pgcollection functions outside change control.

How to Mitigate CVE-2026-96883

Immediate Actions Required

• Upgrade pgcollection to version 2.1.2 or later on every PostgreSQL instance that loads the extension.
• Inventory all databases with SELECT extname, extversion FROM pg_extension WHERE extname = 'pgcollection'; and prioritize public-facing clusters.
• Rotate credentials for any database role that could reach the vulnerable functions if compromise is suspected.
• Review recent PostgreSQL logs for anomalous use of collection functions prior to patching.

Patch Information

AWS released the fix in pgcollection version 2.1.2. Download details are published in the GitHub pgcollection Release v2.1.2 notes and summarized in the AWS Security Bulletin 2026-118. After installing the new package, run ALTER EXTENSION pgcollection UPDATE; in each database that uses the extension.

Workarounds

• Revoke EXECUTE on pgcollection functions from PUBLIC and from any role that does not require collection operations.
• Drop the extension in environments that do not use it with DROP EXTENSION pgcollection; until patching completes.
• Restrict database network exposure so only trusted application hosts can authenticate to PostgreSQL.

# Configuration example
# Identify vulnerable instances
psql -At -c "SELECT current_database(), extname, extversion FROM pg_extension WHERE extname = 'pgcollection';"

# Apply the update after installing pgcollection 2.1.2 packages
psql -c "ALTER EXTENSION pgcollection UPDATE TO '2.1.2';"

# Temporary hardening before patching
psql -c "REVOKE ALL ON SCHEMA pgcollection FROM PUBLIC;"