# amazon-braket-sdk vulnerable to Insecure Deserialization via pickle.loads()

Advisory record · `GHSA-g697-2xrc-gc46`

- **Identifiers:** `GHSA-g697-2xrc-gc46` · `CVE-2026-9291` · `PYSEC-2026-2342`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 25 Jun 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Jun 2026, 18:34 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `amazon-braket-sdk` (PyPI): affected `>=1.10.0, <1.117.0`; fixed in `1.117.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The amazon-braket-sdk package, versions 1.10.0 up to but not including 1.117.0, is vulnerable to insecure deserialization. An attacker with write access to the S3 bucket that stores a Braket job's output can alter the results file so the SDK calls pickle.loads() on attacker-supplied data when the victim retrieves job results, allowing arbitrary code execution with the victim's permissions. Upgrade to amazon-braket-sdk 1.117.0 or later. As a workaround, restrict s3:PutObject permissions on job output buckets to trusted principals only.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`, from CNA (AMZN)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0038, the 32nd percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:01 UTC: First seen by agentprime
- 31 Oct 2026, 15:01 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-g697-2xrc-gc46)

## Sources

- [GitHub Advisory Database: GHSA-g697-2xrc-gc46](https://github.com/advisories/GHSA-g697-2xrc-gc46)
- [OSV: GHSA-g697-2xrc-gc46](https://osv.dev/vulnerability/GHSA-g697-2xrc-gc46)
- <https://github.com/amazon-braket/amazon-braket-sdk-python/security/advisories/GHSA-g697-2xrc-gc46>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-9291>
- <https://aws.amazon.com/security/security-bulletins/2026-036-aws>
- <https://github.com/amazon-braket/amazon-braket-sdk-python>
- <https://github.com/amazon-braket/amazon-braket-sdk-python/releases/tag/v1.117.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-g697-2xrc-gc46>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-g697-2xrc-gc46/>. Everything for agents: <https://agentprime.io/llms.txt>.
