CVE-2026-96883: AWS pgcollection · Type Confusion
Affects AWS pgcollectionSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · patch available : patch AWS pgcollection soon.
Data as of 13 Nov 2026, 23:54 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.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Total control over the software or total information disclosure
CISA SSVC assessment, 2026-09-24.
- Patch
- Available
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 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AWSpgcollection | 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
Users should upgrade AWS pgcollection to version 2.1.2 or later to remediate this vulnerability. Since this is a cloud service managed by AWS, verify with the AWS security bulletin for any additional mitigation steps or confirmation of server-side patching.
Description
CVE-2026-96883 is a high-severity type confusion vulnerability in AWS pgcollection versions 2.0.0 through 2.1.1. This flaw allows an authenticated remote user to execute arbitrary code as the postgres operating system user by exploiting mismatched type metadata in collection value retrieval and array conversion functions. The issue is resolved in version 2.1.2 and later.