---
id: "GHSA-69c4-mvf5-5xm3"
kind: "vulnerability"
aliases: ["GHSA-69c4-mvf5-5xm3"]
title: "CVE-2026-108096: Improper authorization in query resolvers for SQL-backed models in AWS Amplify API Category"
severity: "high"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["appsync", "aws", "aws-amplify", "graphql", "javascript", "lab-disclosure", "package", "typescript"]
not_affected_if: ["fixed-version", "no-sql-backed-models"]
published_at: null
first_seen_at: "2026-10-24T19:28:16+00:00"
updated_at: "2026-10-25T04:50:17+00:00"
sources: [{"source": "lab", "url": "https://aws.amazon.com/security/security-bulletins/rss/2026-133-aws/", "first_seen_at": "2026-10-24T19:28:16+00:00"}]
---

# CVE-2026-108096: Improper authorization in query resolvers for SQL-backed models in AWS Amplify API Category

Query resolvers generated for SQL-backed models in the Amplify API Category skip proper authorization checks, so a signed-in user can craft GraphQL queries to read records owned by other users of the same application. The fix is in the updated index transformer and the constructs that bundle it, and no workaround is documented.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed `@aws-amplify/graphql-index-transformer` version in `package.json` and lockfile; affected if below `3.1.2`
- Check `@aws-amplify/graphql-api-construct` (affected below `1.21.4`) and `@aws-amplify/data-construct` (affected below `1.17.4`)
- Confirm whether the backend uses SQL-backed models with query resolvers and authorization rules

## Fix

- Upgrade `@aws-amplify/graphql-index-transformer` to `3.1.2`
- Upgrade `@aws-amplify/data-construct` to `1.17.4` or `@aws-amplify/graphql-api-construct` to `1.21.4`
- Patch any forked or derivative code, then redeploy the backend

## Timeline

- 2026-10-24T19:28:16+00:00 lab https://aws.amazon.com/security/security-bulletins/rss/2026-133-aws/ — AWS: CVE-2026-108096: Improper authorization in query resolvers for SQL-backed models in AWS Amplify API Category

## Documents

- [advisory] AWS: CVE-2026-108096: Improper authorization in query resolvers for SQL-backed models in AWS Amplify API Category https://aws.amazon.com/security/security-bulletins/rss/2026-133-aws/

## From the sources

CVE-2026-108096: Improper authorization in query resolvers for SQL-backed models in AWS Amplify API Category

### CVE-2026-108096: Improper authorization in query resolvers for SQL-backed models in AWS Amplify API Category

Bulletin ID: 2026-133-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/09/2026 11:00 AM PDT

Description:

AWS Amplify API Category is a CDK Construct library for defining GraphQL data models with authorization rules as AWS AppSync APIs. We identified CVE-2026-108096, where improper authorization in the query resolvers generated by @aws-amplify/graphql-index-transformer might allow an authenticated remote user to read records owned by other users of the same application via crafted queries.

Impacted versions:

- @aws-amplify/graphql-index-transformer >=2.2.0, <3.1.2;
- @aws-amplify/graphql-api-construct >=1.4.0, <1.21.4;
- @aws-amplify/data-construct <1.17.4

Resolution:

This issue has been addressed in @aws-amplify/graphql-index-transformer 3.1.2 (included in @aws-amplify/data-construct 1.17.4 and @aws-amplify/graphql-api-construct 1.21.4). We recommend upgrading to the latest version ensuring any forked or derivative code is patched to incorporate the new fixes and then redeploying their backend.

Workarounds:

No workarounds are available.

References:

- CVE-2026-108096
- GHSA-69c4-mvf5-5xm3

 Please email aws-security@amazon.com with any security questions or concerns.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_