Skip to main content

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:

  • CVE-2026-124034: amazon-braket-sdk >= 1.10.0 AND < 1.127.7
  • CVE-2026-124035: amazon-braket-schemas >= 1.17.0 AND < 1.32.2

Resolution:

  • CVE-2026-124034: This issue has been addressed in Amazon Braket SDK version 1.127.7. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
  • CVE-2026-124035: This issue has been addressed in Amazon Braket Schemas version 1.32.2. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.

Workarounds:

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.