---
id: "CVE-2026-108096"
kind: "vulnerability"
aliases: ["CVE-2026-108096"]
title: "AWS Amplify GraphQL: crafted queries read other users' records in SQL-backed models"
severity: "high"
cvss: 7.1
epss: 0.00299
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["aws", "aws-amplify", "aws-appsync", "graphql", "lab-disclosure", "package", "self-hosted", "sql"]
not_affected_if: ["no-amplify-graphql", "unaffected-versions"]
published_at: "2026-10-09T18:17:06+00:00"
first_seen_at: "2026-10-24T19:28:16+00:00"
updated_at: "2026-10-25T12:38:49+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"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-108096", "first_seen_at": "2026-10-24T20:15:27+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-108096", "first_seen_at": "2026-10-25T12:38:49+00:00"}]
---

# AWS Amplify GraphQL: crafted queries read other users' records in SQL-backed models

Query resolvers generated by the Amplify GraphQL index transformer fail to check authorization properly for SQL-backed models. An authenticated user can read records owned by other users of the same application through crafted queries.

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

## How to check

- Check the installed versions of `@aws-amplify/graphql-index-transformer`, `@aws-amplify/graphql-api-construct` and `@aws-amplify/data-construct` in the backend's lockfile, e.g. `npm ls @aws-amplify/graphql-index-transformer`
- Confirm whether the backend uses SQL-backed models (unknown from the sources whether this changes exposure)

## Fix

- Upgrade `@aws-amplify/graphql-index-transformer` to `3.1.2` or later
- Upgrade `@aws-amplify/graphql-api-construct` to `1.21.4` or later
- Upgrade `@aws-amplify/data-construct` to `1.17.4` or later
- Redeploy the backend after upgrading; patch any forked or derivative code too (no workarounds are available)

## 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
- 2026-10-24T20:15:27+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-108096
- 2026-10-25T12:38:49+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-108096

## 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_