Unsafe reflection in Amazon Braket Schemas error mitigation validation
Affects amazon-braket-schemas 1.17.0 up to but not including 1.32.2 on machines that retrieve quantum task results with the Amazon Braket SDK. Fixed in 1.32.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.32.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. amazon-braket-schemas versions >=1.17.0 and <1.32.2 are affected The issue occurs under certain circumstances in the error mitigation schema validation, which imports and calls Python code named in a quantum task result document The victim's machine must retrieve the affected task results with the Amazon Braket SDK and Amazon Braket Schemas
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Unsafe reflection in the error mitigation schema validation in Amazon Braket Schemas before 1.32.2 might allow a remote authenticated user with S3 write access to the quantum task output location to execute arbitrary code on any machine that retrieves the quantum task results via a crafted task result document.
We recommend you upgrade to amazon-braket-schemas version 1.32.2 or later.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
amazon-braket-schemas versions >=1.17.0 and <1.32.2 are affected The issue occurs under certain circumstances in the error mitigation schema validation, which imports and calls Python code named in a quantum task result document The victim's machine must retrieve the affected task results with the Amazon Braket SDK and Amazon Braket SchemasUpgrade to a fixed version: 1.32.2.
Workaround: Restrict S3 write access to the Braket task-output and local-job input data locations to trusted principals
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Amazon amazon-braket-schemas
From 1.17.0 · fixed in 1.32.2
Evidence 3
- Advisory
- Advisory
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124035
Is CVE-2026-124035 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Under certain circumstances, the error mitigation schema validation imports and calls Python code named in a quantum task result document. This could let arbitrary code run with the privileges of the user retrieving the results.Source: aws.amazon.com, github.com
Which versions are affected by CVE-2026-124035?
amazon-braket-schemas: from 1.17.0 before 1.32.2.Source: cve.now feed data
Am I affected, and how do I check?
Versions 1.17.0 up to but not including 1.32.2 of amazon-braket-schemas are affected. The issue applies on any machine that retrieves quantum task results with the Amazon Braket SDK and Amazon Braket Schemas; the installed version can be checked with pip show amazon-braket-schemas.Source: aws.amazon.com, github.com
How do I fix CVE-2026-124035?
Upgrade amazon-braket-schemas to version 1.32.2 or later, which addresses this issue. Until then, restrict S3 write access to the Braket task-output and local-job input data locations to trusted principals.Source: aws.amazon.com, github.com