amazon-braket-sdk
Affected
- introduced
1.10.0, fixed1.117.0(ecosystem)
Fixed versions
1.117.0
Fix
- Fixed version
1.117.0pip install --upgrade amazon-braket-sdk==1.117.0
Advisory
Also known as: CVE-2026-9291, PYSEC-2026-2342
amazon-braket-sdk vulnerable to Insecure Deserialization via pickle.loads()
Summary
Amazon Braket SDK is an open-source Python library for interacting with the Amazon Braket quantum computing service, including managing hybrid quantum jobs and retrieving job results. An issue exists where, under certain circumstances, a remote authenticated user with S3 write access to a Braket job output bucket can achieve arbitrary code execution by exploiting insecure deserialization in the job results processing component.
Impact
The SDK's deserialize_values() function reads the dataFormat field directly from the job results JSON file without validation. An actor with write access to the victim's S3 job output bucket can modify the dataFormat field in results.json from PLAINTEXT to pickled_v4 and replace dataDictionary values with base64-encoded executable payloads. When the victim calls job.result(), load_job_result(), or load_job_checkpoint() as part of their normal Braket workflow, the SDK calls pickle.loads() on the actor-controlled data, executing arbitrary code with the victim's permissions.
Impacted versions: >= v1.10.0 AND < 1.117.0
Patches
This issue has been addressed in amazon-braket-sdk version 1.117.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.
Workarounds
If users cannot upgrade immediately:
References
If users have any questions or comments about this advisory, amazon-braket-sdk asks that users contact AWS Security via the vulnerability reporting page or directly via email to [[email protected]](mailto:[email protected]). Please do not create a public GitHub issue.
High Basis: The source's own band: HIGH
1.10.0, fixed 1.117.0 (ecosystem)1.117.0
1.117.0pip install --upgrade amazon-braket-sdk==1.117.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0