CVE-2026-96883: Type confusion in AWS pgcollection allows remote code execution
Affects pgcollectionSource AWS Security Bulletins
Not known to be exploited · CVSS 8.8 High · fixed in 2.1.2 : patch pgcollection soon.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.1.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubpgcollectionpkg:github/pgcollectionOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in pgcollection version 2.1.2. Users who have deployed pgcollection versions 2.0.0 through 2.1.1 should upgrade to version 2.1.2 or later. Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL customers are not impacted and require no action. No workarounds are available.
Description
CVE-2026-96883 is a type confusion vulnerability in the pgcollection extension for PostgreSQL. It arises from incorrect type coercion logic when an authenticated user requests a stored icollection value as a type incompatible with its actual stored type. This flaw can cause the PostgreSQL backend to crash or allow arbitrary code execution. The vulnerability affects pgcollection versions 2.0.0 through 2.1.1. It has been fixed in version 2.1.2. Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL are not impacted as they ship version 1.1.1, which does not contain this issue. No workarounds are available.