AWS Braket SDK and Schemas Updates Fix File Write and Code Execution Flaws

P1 — VALIDATE AND UPDATEHigh (CVE-2026-124035); Medium (CVE-2026-124034) · 7.1 (CVE-2026-124035); 6.4 (CVE-2026-124034), project CVSS v3.1 base scoresEXPLOITATION: NOT STATED

Quick Answer

Upgrade Braket SDK to 1.127.7 and Schemas to 1.32.2 or later. Restrict S3 input and output writers, rebuild dependent environments, and test local jobs and result retrieval.

Confirm Scope And Apply The Supported Remediation

What to do now: Record both Python package versions in notebooks, local-job hosts and runners, task-result consumers, S3 locations and IAM write grants. The SDK traversal affects local hybrid jobs, not hybrid jobs run by the Braket service. The schemas issue affects a machine retrieving results from an attacker-writable task output location. Upgrade both packages and maintained forks. Restrict write access to task outputs, local-job inputs and the associated IAM role to trusted principals. Confirm loaded package versions after restarting Python processes, test expected jobs and results, review unexpected files or process execution where exposure existed, and retain dependency-lock and S3 audit evidence.

Open the authoritative advisory

Last verified: 2026-11-10 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeAmazon Braket SDK and Amazon Braket Schemas for Python
Advisory2026-175-AWS / GHSA-4hhf-mfx9-3877 / GHSA-9r5x-g8jm-9mjj
CVEsCVE-2026-124034, CVE-2026-124035
Authoritative release dateNovember 9, 2026 at 14:15 PST (22:15 UTC), from AWS bulletin 2026-175-AWS.
Authority revision dateNo later revision stated.
Affected versionsamazon-braket-sdk >=1.10.0 and <1.127.7 for local hybrid job input downloads; amazon-braket-schemas >=1.17.0 and <1.32.2 for task-result error-mitigation validation. An attacker needs S3 write access to the respective input or output location.
Fixed versionamazon-braket-sdk 1.127.7 or later; amazon-braket-schemas 1.32.2 or later
CVSS base score7.1 (CVE-2026-124035); 6.4 (CVE-2026-124034), project CVSS v3.1 base scores
CVSS severityHigh (CVE-2026-124035); Medium (CVE-2026-124034)
Exploitation statusAWS does not state exploitation in these advisories.; no exploitation claim is inferred.

What Changed

AWS fixed local input-download traversal in Braket SDK and unsafe Python reflection in Braket Schemas. The first permits file writes on a local hybrid-job host; the second can execute code when a user retrieves crafted task results. The schemas fix follows an earlier remediation for CVE-2026-9291.

What To Validate Now

  1. Inventory. Record both Python package versions in notebooks, local-job hosts and runners, task-result consumers, S3 locations and IAM write grants.
  2. Establish applicability. The SDK traversal affects local hybrid jobs, not hybrid jobs run by the Braket service. The schemas issue affects a machine retrieving results from an attacker-writable task output location.
  3. Remediate. Upgrade both packages and maintained forks. Restrict write access to task outputs, local-job inputs and the associated IAM role to trusted principals.
  4. Validate. Confirm loaded package versions after restarting Python processes, test expected jobs and results, review unexpected files or process execution where exposure existed, and retain dependency-lock and S3 audit evidence.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Updating only the SDK does not establish that a separately constrained Schemas dependency is fixed. The SDK flaw does not directly provide file reads or code execution; keep its impact separate from the schemas flaw.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.