{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-108096 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-108096 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-108096 is a high-severity missing authorization vulnerability in aws-amplify/data-construct, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-108096 and fix it if it is affected.\n\nWhat it is: CVE-2026-108096 is a high-severity missing authorization vulnerability in aws-amplify/data-construct, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-108096 in the wild and no public exploit code.\n\nAffected product: aws-amplify/data-construct. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-108096/ (Markdown: https://insights.sbomify.com/CVE-2026-108096/index.md)","id":"CVE-2026-108096","markdown":"https://insights.sbomify.com/CVE-2026-108096/index.md","name":"CVE-2026-108096","record":{"aliases":["GHSA-69c4-mvf5-5xm3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"AWS Amplify GraphQL library","requires_auth":"low_privilege","summary":"An authenticated user can read other users' records in AWS Amplify applications due to improper authorization in GraphQL query resolvers.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Improper authorization in the query resolvers generated by @aws-amplify/graphql-index-transformer in AWS Amplify API Category before 3.1.2 might allow an authenticated remote user to read records owned by other users of the same application via crafted queries.\n\nThis issue has been addressed in @aws-amplify/graphql-index-transformer  3.1.2 https://www.npmjs.com/package/@aws-amplify/graphql-index-transformer/v/3.1.2  (included in @aws-amplify/data-construct  1.17.4 https://www.npmjs.com/package/@aws-amplify/data-construct/v/1.17.4  and @aws-amplify/graphql-api-construct  1.21.4 https://www.npmjs.com/package/@aws-amplify/graphql-api-construct/v/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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Improper authorization in query resolvers for SQL-backed models in AWS Amplify API Category","id":"CVE-2026-108096","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"HortusFox before 6.2 SQL Injection via /api/locations/list include_info Parameter","id":"CVE-2026-108100"},"packages":[],"prev":{"headline":"Mutter: mutter: client-triggered use-after-free in wayland color-management icc image description path","id":"CVE-2026-108094"},"products":["aws-amplify/data-construct","aws-amplify/graphql-api-construct","aws-amplify/graphql-index-transformer"],"published":"2026-10-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-20","vendors":["AWS"]},"summary":"An authenticated user can read other users' records in AWS Amplify applications due to improper authorization in GraphQL query resolvers.","url":"https://insights.sbomify.com/CVE-2026-108096/"}