Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-g697-2xrc-gc46

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

CVSS 7.5 HighEPSS 0.0038 · 32nd percentile

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.

PackageEcosystemAffectedFixed in
amazon-braket-sdkPyPI>=1.10.0, <1.117.01.117.0
Identifiers
GHSA-g697-2xrc-gc46 · CVE-2026-9291 · PYSEC-2026-2342
Weakness (CWE)
CWE-502
Tags
Published
25 Jun 2026
Updated
13 Jul 2026

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

ScoreRatingCVSSVectorSource
7.5 High 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 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

  1. 31 Oct 2026, 15:01 UTC First seen by agentprime
  2. 31 Oct 2026, 15:01 UTC Confirmed by OSV

Sources

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.