Quick answers
- Is CVE-2026-96883 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96883 being exploited in the wild.
- How severe is CVE-2026-96883?
- High severity, with a CVSS score of 8.8, published 24 September 2026.
- Which products and versions are affected?
- AWS Pgcollection 2.0.0 through 2.1.1.
- Is there a fix for CVE-2026-96883?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-96883 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-96883?
- Check whether you run Amazon AWS or AWS Pgcollection at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
CVE-2026-96883 is a type confusion vulnerability in pgcollection's type coercion logic affecting versions 2.0.0 through 2.1.1. The vulnerability arises when an authenticated database user requests an icollection value using a type incompatible with how the value was stored, causing the extension to misinterpret the datum's binary representation. This type confusion can lead to out-of-bounds memory access or control flow hijacking, enabling a database-authenticated attacker to crash the PostgreSQL backend or execute arbitrary code within the database process context. No patch information is currently available in the advisory, though the vendor (AWS) was aware of the issue as of the publication date.
Affected products
- AWS pgcollection 2.0.0 through 2.1.1
Timeline
- 2026-09-24: disclosed: AWS security bulletin 2026-118-AWS published