Skip to content

← Actionable
High, CVSS 7.5amended

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

CVE-2026-9291GHSA-g697-2xrc-gc46

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (amazon-braket-sdk 1.117.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.5 · 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 · score source
EPSS
  • CVE-2026-9291: 0.38% estimated exploitation activity in the next 30 days; percentile 32.10 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 deserializevalues() 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 pickledv4 and replace dataDictionary values with base64-encoded executable payloads. When the victim calls job.result(), loadjobresult(), or loadjobcheckpoint() as part of their normal Braket workflow, the SDK calls pickle.loads() on the actor-controlled data, executing arbitrary code with the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-g697-2xrc-gc46

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-g697-2xrc-gc46

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-9291

Advisory: amazon-braket-sdk vulnerable to Insecure Deserialization via pickle.loads()
IDs: CVE-2026-9291, GHSA-g697-2xrc-gc46
Record: https://patchnext.com/advisories/cve-2026-9291 (revision 3, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: amazon-braket-sdk 1.117.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI amazon-braket-sdk: affected >= 1.10.0, < 1.117.0; fixed in 1.117.0

## Suggested inspection (read-only)
- `python -m pip show amazon-braket-sdk`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on amazon-braket-sdk.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g697-2xrc-gc46 (OSV record GHSA-g697-2xrc-gc46 lists affected ranges: PyPI amazon-braket-sdk >=1.10.0 <1.117.0 (fixed))
- Verified: https://github.com/advisories/GHSA-g697-2xrc-gc46 (GitHub-reviewed advisory GHSA-g697-2xrc-gc46 lists affected ranges: PyPI amazon-braket-sdk >=1.10.0 <1.117.0)

Commands are suggestions: review each one before running it.

Loading voting…