AMAZON-BRAKET-SDK · CVE-2026-9291 · Package
FIX → 1.117.0
The Amazon Braket SDK for Python calls pickle.loads on data it reads, so it can run attacker-supplied code when it loads untrusted input. An attacker who can supply that input can get code execution on the machine running the SDK.
first public May 22, 2026 · 3 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams that run the Amazon Braket SDK for Python at a version from 1.10.0 up to but not including 1.117.0. The AWS bulletin for the follow-on CVEs ties the risk to users with S3 write access to task-output or hybrid-job input locations, so teams that tightly restrict those locations are less exposed; the sources do not confirm the same path for CVE-2026-9291 itself.
Not affected if no-braket-sdk-use, upgraded-to-1.117.0
Who cares amazon-braket, amazon-braket-sdk, aws, lab-disclosure, python, quantum
pip show amazon-braket-sdk and compare the version with the affected range (>= 1.10.0, < 1.117.0).Upgrade to 1.117.0
CVE-2026-124034, CVE-2026-124035: Issues with Amazon Braket SDK
Bulletin ID: 2026-175-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 11/09/2026 14:15 PM PST
Description:
Amazon Braket SDK is an open source Python library that customers use to run quantum tasks and hybrid jobs on Amazon Braket and retrieve their results, and it uses the Amazon Braket Schemas library to parse task results.
We identified CVE-2026-124034, an issue in the local hybrid job input data download in the Amazon Braket SDK. A remote authenticated user with S3 write access to a hybrid job's input data location might be able to overwrite arbitrary files, with the privileges of the user running the job, by supplying crafted S3 object keys.
We identified CVE-2026-124035, an issue in the error mitigation schema validation in Amazon Braket Schemas, the library the Amazon Braket SDK uses to parse quantum task results. A remote authenticated user with S3 write access to the quantum task output location might be able to execute arbitrary code on any machine that retrieves the quantum task results by supplying a crafted task result document. Please note, this is a follow-on fix to the prior advisory CVE-2026-9291.
Impacted versions:
Resolution:
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
1.117.0Workarounds:
Restrict S3 write access to the Braket task-output and local-job input data locations (and the job's IAM role) to trusted principals.
References:
Acknowledgement:
We would like to thank Eva Crystal (0xiviel), XSource Security for collaborating on this issue through the coordinated issue disclosure process.
Please email aws-security@amazon.com with any s ecurity questions or concerns.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.