Unsafe Deserialization in amazon-braket-sdk (CVE-2026-9291)
Summary
Vulnerability in amazon-braket-sdk (CVE-2026-9291). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.117.0 or later.
Original description
The description as published by the source.
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:
- Restrict S3 bucket policies on the Braket job output buckets to enforce least-privilege access, ensuring only trusted principals have s3:PutObject p…
Source: AWS Security Bulletins NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-9291 has been found in amazon-braket-sdk.
Successful exploitation can lead to full system takeover. CVSS score: 7.1/10.
What to do: upgrade amazon-braket-sdk to 1.117.0 or later.
If unsure, ask your IT team or search "amazon-braket-sdk CVE-2026-9291" on the vendor's site.
CVE-2026-9291 (amazon-braket-sdk) — CWE-502 / CVSS v3 7.1
Attack vector: remote (network-reachable)
Patched: 1.117.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in amazon-braket-sdk.
Check the vendor advisory for the affected versions of amazon-braket-sdk.
Severity: High (CVSS 7.1/10). Successful exploitation can lead to full system takeover.
Update to 1.117.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'amazon-braket-sdk' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'amazon-braket-sdk' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
amazon-braket-sdkを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade amazon-braket-sdk to 1.117.0ステージング環境で 1.117.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- AWS aws.amazon.com
- package github.com
- web github.com
- web aws.amazon.com
- web github.com
- web github.com
- web aws.amazon.com