AWS Updates pgcollection to Address Type-Confusion Remote Code Execution
Tech GuruQuick Answer
AWS published 2026-118-AWS for pgcollection. Self-managed users of versions 2.0.0 through 2.1.1 should move to 2.1.2 or later. AWS states that existing Amazon RDS for PostgreSQL and Aurora PostgreSQL releases ship unaffected version 1.1.1.
Confirm Scope And Apply The Supported Fix
What to do now: Inventory pgcollection versions, distinguish self-managed deployments from the AWS managed-service versions described in the bulletin, upgrade affected 2.0.0–2.1.1 installations to 2.1.2 or later, validate database behavior, and retain evidence.
Last verified: 2026-09-27 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | pgcollection extension releases 2.0.0 through 2.1.1 |
|---|---|
| Advisory | 2026-118-AWS |
| CVE | CVE-2026-96883 |
| Authoritative release date | 2026-09-24 19:00:00 UTC |
| Authority revision date | No separate revision date published |
| Affected versions | pgcollection 2.0.0 through 2.1.1. AWS states that existing Amazon RDS for PostgreSQL and Aurora PostgreSQL releases ship unaffected pgcollection 1.1.1. |
| Fixed version | pgcollection 2.1.2 or later |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
AWS states that a type-confusion flaw in pgcollection 2.0.0 through 2.1.1 could allow remote code execution. Version 2.1.2 fixes the issue; AWS publishes no workaround.
What To Validate Now
- Inventory. Locate PostgreSQL environments using pgcollection, record the extension version and deployment model, and identify owners and exposed application paths.
- Establish applicability. Match each installation to AWS's affected range of pgcollection 2.0.0 through 2.1.1. Record AWS's explicit statement about existing RDS and Aurora PostgreSQL version 1.1.1 rather than inferring managed-service applicability.
- Remediate. Upgrade affected installations to pgcollection 2.1.2 or later. AWS publishes no workaround.
- Validate. Confirm the extension version, validate dependent queries and application paths, review database and application logs for anomalies, and document managed-service or self-managed applicability.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Back up configuration and application data and test dependent queries before broad rollout. AWS does not state that exploitation has occurred, and severity must not be inferred from the impact description.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
