{"id":"GHSA-g539-cj32-hv6r","kind":"vulnerability","aliases":["GHSA-g539-cj32-hv6r"],"related":[],"title":"CVE-2026-96883 - Type confusion in AWS pgcollection allows remote code execution","description":"CVE-2026-96883 - Type confusion in AWS pgcollection allows remote code execution\n\n### CVE-2026-96883 - Type confusion in AWS pgcollection allows remote code execution\n\nBulletin ID: 2026-118-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 09/24/2026 12:00 PM PDT\n\nDescription:\n\npgcollection is an open source extension to PostgreSQL. We identified CVE-2026-96883, an issue in pgcollection's type coercion logic. When requesting a stored icollection value as a type incompatible with how it was actually stored causes the extension to misinterprets the datum's representation, allowing an authenticated database user to crash the PostgreSQL backend or execute arbitrary code.\n\nImpacted versions: pgcollection v2.0.0 through v2.1.1\n\nResolution:\n\nThis issue has been addressed in pgcollection version 2.1.2. This issue does not impact existing Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL customers. These services only ship 1.1.1 version, which does not contain this issue.\n\nCustomers who downloaded and compiled pgcollection 2.0.0 through 2.1.1 from the AWS GitHub repository and deployed them in their own PostgreSQL environments should upgrade to version 2.1.2 or later.\n\nWorkarounds:\n\nNone.\n\nReferences:\n\n- CVE-2026-96883 \n- GHSA-g539-cj32-hv6r\n\n Please email aws-security@amazon.com with any security questions or concerns.","summary":"pgcollection, an open source PostgreSQL extension from AWS, mishandles a stored collection value when it is requested as an incompatible type. An authenticated database user can crash the PostgreSQL backend or execute arbitrary code.","severity":"high","cvss":null,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["aws","lab-disclosure","package","pgcollection","postgresql","self-hosted"],"not_affected_if":["managed-hosting","rds-or-aurora"],"how_to_check":"- Check the installed pgcollection version in each PostgreSQL database with `SELECT extversion FROM pg_extension WHERE extname = 'pgcollection';` and whether it is 2.0.0 through 2.1.1\n- Confirm whether the database is self-hosted with pgcollection compiled from the AWS GitHub repository; RDS and Aurora ship 1.1.1 and are not affected","fix":"- Upgrade self-hosted pgcollection to `2.1.2` or later\n- No workaround is published by AWS","status":"open","published_at":"2026-09-24T00:00:00+00:00","first_seen_at":"2026-10-24T20:05:35+00:00","triaged_at":"2026-10-25T05:30:22+00:00","updated_at":"2026-10-25T05:30:22+00:00","category":"package","confidence":0.7,"triage":{"at":"2026-10-25T05:30:22Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade self-hosted pgcollection to `2.1.2` or later\n- No workaround is published by AWS","reach":"network","title":"AWS pgcollection: type confusion lets a database user run code","impact":"high","summary":"pgcollection, an open source PostgreSQL extension from AWS, mishandles a stored collection value when it is requested as an incompatible type. An authenticated database user can crash the PostgreSQL backend or execute arbitrary code.","category":"package","nicknames":[],"who_cares":["postgresql","self-hosted","pgcollection"],"confidence":0.7,"needs_auth":"yes","worst_case":"Authenticated database user runs arbitrary code on the PostgreSQL server","analyst_note":"","how_to_check":"- Check the installed pgcollection version in each PostgreSQL database with `SELECT extversion FROM pg_extension WHERE extname = 'pgcollection';` and whether it is 2.0.0 through 2.1.1\n- Confirm whether the database is self-hosted with pgcollection compiled from the AWS GitHub repository; RDS and Aurora ship 1.1.1 and are not affected","needs_analyst":false,"not_affected_if":["managed-hosting","rds-or-aurora"],"who_is_affected":"Teams that compiled and deployed pgcollection 2.0.0 through 2.1.1 from the AWS GitHub repository into their own PostgreSQL servers. Amazon RDS for PostgreSQL and Aurora PostgreSQL customers are not affected because those services ship pgcollection 1.1.1.","user_interaction":"no","needs_special_setup":"yes","severity_if_unknown":"high"},"cost_usd":0.000673,"input_tokens":3796,"output_tokens":587,"severity_before":"unknown"},"analyst_status":null,"analyst_note":null,"search":"'-118':94C '-2026':2A,68C,80C,122C,247C '-96883':3A,69C,81C,123C,248C '00':107C '09/24/2026':105C '1.1.1':206C '12':106C '2.0.0':220C '2.1.1':222C '2.1.2':186C,240C '2026':93C 'actual':146C 'address':182C 'allow':9A,75C,87C,157C 'amazon':193C,198C 'arbitrari':65B,169C 'attent':102C 'aurora':199C 'authent':55B,159C 'aw':7A,23B,40B,73C,85C,95C,97C,225C 'aws-security@amazon.com':256C 'backend':62B,166C 'bulletin':91C 'caus':148C 'cj32':16A,21A,252C 'code':11A,66B,77C,89C,170C 'coercion':130C 'collect':44B 'compil':218C 'concern':262C 'confus':5A,71C,83C 'contain':211C 'content':98C 'crash':59B,163C 'custom':201C,214C 'cve':1A,67C,79C,121C,246C 'databas':56B,160C 'date':104C 'datum':154C 'deploy':229C 'descript':110C 'disclosur':26B 'download':216C 'email':255C 'environ':235C 'execut':12A,64B,78C,90C,168C 'exist':192C 'extens':38B,116C,150C 'g539':15A,20A,251C 'ghsa':14A,19A,250C 'ghsa-g539-cj32-hv6r':13A,18A,249C 'github':226C 'host':32B 'hv6r':17A,22A,253C 'icollect':136C 'id':92C 'identifi':120C 'impact':171C,191C 'import':100C 'incompat':52B,141C 'issu':125C,179C,188C,213C 'lab':25B 'lab-disclosur':24B 'later':242C 'logic':131C 'mishandl':41B 'misinterpret':152C 'none':244C 'open':35B,114C 'packag':27B 'pdt':109C 'pgcollect':8A,28B,33B,74C,86C,111C,127C,173C,184C,219C 'pleas':254C 'pm':108C 'postgresql':29B,37B,61B,118C,165C,196C,200C,234C 'public':103C 'question':260C 'rds':194C 'refer':245C 'remot':10A,76C,88C 'repositori':227C 'represent':156C 'request':49B,133C 'requir':101C 'resolut':177C 'scope':96C 'secur':259C 'self':31B 'self-host':30B 'servic':203C 'ship':205C 'sourc':36B,115C 'store':43B,135C,147C 'type':4A,53B,70C,82C,99C,129C,140C 'upgrad':237C 'user':57B,161C 'v2.0.0':174C 'v2.1.1':176C 'valu':45B,137C 'version':172C,185C,207C,239C 'workaround':243C","nicknames":[],"mitigations":[],"who_affected":"Teams that compiled and deployed pgcollection 2.0.0 through 2.1.1 from the AWS GitHub repository into their own PostgreSQL servers. Amazon RDS for PostgreSQL and Aurora PostgreSQL customers are not affected because those services ship pgcollection 1.1.1.","tier":"B","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-09-24T00:00:00+00:00","kev":null,"cvss_vector":null,"cvss_by":null,"poc_count":0,"sources":[{"source":"lab","external_id":"https://aws.amazon.com/security/security-bulletins/rss/2026-118-aws/#GHSA-g539-cj32-hv6r","url":"https://aws.amazon.com/security/security-bulletins/rss/2026-118-aws/","severity":null,"published_at":"2026-09-24T00:00:00+00:00","modified_at":null,"first_seen_at":"2026-10-24T20:05:35+00:00","fetched_at":"2026-10-25T19:56:21+00:00","note":"AWS: CVE-2026-96883 - Type confusion in AWS pgcollection allows remote code execution"}],"documents":[{"id":2971,"url":"https://aws.amazon.com/security/security-bulletins/rss/2026-118-aws/","title":"AWS: CVE-2026-96883 - Type confusion in AWS pgcollection allows remote code execution","kind":"advisory","source":"lab","text":"CVE-2026-96883 - Type confusion in AWS pgcollection allows remote code execution\n\n### CVE-2026-96883 - Type confusion in AWS pgcollection allows remote code execution\n\nBulletin ID: 2026-118-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 09/24/2026 12:00 PM PDT\n\nDescription:\n\npgcollection is an open source extension to PostgreSQL. We identified CVE-2026-96883, an issue in pgcollection's type coercion logic. When requesting a stored icollection value as a type incompatible with how it was actually stored causes the extension to misinterprets the datum's representation, allowing an authenticated database user to crash the PostgreSQL backend or execute arbitrary code.\n\nImpacted versions: pgcollection v2.0.0 through v2.1.1\n\nResolution:\n\nThis issue has been addressed in pgcollection version 2.1.2. This issue does not impact existing Amazon RDS for PostgreSQL and Amazon Aurora PostgreSQL customers. These services only ship 1.1.1 version, which does not contain this issue.\n\nCustomers who downloaded and compiled pgcollection 2.0.0 through 2.1.1 from the AWS GitHub repository and deployed them in their own PostgreSQL environments should upgrade to version 2.1.2 or later.\n\nWorkarounds:\n\nNone.\n\nReferences:\n\n- CVE-2026-96883 \n- GHSA-g539-cj32-hv6r\n\n Please email aws-security@amazon.com with any security questions or concerns.","published_at":"2026-09-24T00:00:00+00:00","relation":"advisory","confidence":null,"note":null}],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}