Quick answers
- Is CVE-2026-108096 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108096 being exploited in the wild.
- How severe is CVE-2026-108096?
- High severity, with a CVSS score of 6.5, published 9 October 2026.
- Which products and versions are affected?
- AWS @Aws-Amplify/Data-Construct <1.17.4; AWS @Aws-Amplify/Graphql-Api-Construct >=1.4.0, <1.21.4; AWS @Aws-Amplify/Graphql-Index-Transformer >=2.2.0, <3.1.2.
- Is there a fix for CVE-2026-108096?
- Yes: fixed in @aws-amplify/graphql-index-transformer 3.1.2, @aws-amplify/graphql-api-construct 1.21.4, @aws-amplify/data-construct 1.17.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-108096 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-108096?
- Check whether you run Amazon AWS, AWS @Aws-Amplify/Data-Construct, AWS @Aws-Amplify/Graphql-Api-Construct or one of the others listed 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.
How to fix
- Fixed in: @aws-amplify/graphql-index-transformer 3.1.2, @aws-amplify/graphql-api-construct 1.21.4, @aws-amplify/data-construct 1.17.4
Technical details
Improper authorization in the query resolvers generated by the @aws-amplify/graphql-index-transformer allows authenticated remote attackers to bypass record ownership checks and read data via crafted GraphQL queries. The vulnerability affects SQL-backed models where authorization rules are intended to restrict access. A patch is available in versions 3.1.2 and later.
Affected products
- AWS @aws-amplify/graphql-index-transformer >=2.2.0, <3.1.2
- AWS @aws-amplify/graphql-api-construct >=1.4.0, <1.21.4
- AWS @aws-amplify/data-construct <1.17.4
Timeline
- 2026-10-09: disclosed