# CVE-2026-8597: Missing integrity verification in Triton inference handler in Amazon SageMaker Python SDK

> An authenticated attacker with S3 write access can achieve code execution in inference containers by replacing model artifacts with malicious pickle payloads.

- **Severity:** Medium 6.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 May 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-rq6v-x3j8-7qgf, PYSEC-2026-3060

## What is CVE-2026-8597?

CVE-2026-8597 is a medium-severity unsafe deserialization vulnerability in AWS Amazon SageMaker Python SDK, published on 14 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Missing integrity verification in the Triton inference handler in Amazon SageMaker Python SDK v2 before v2.257.2 and v3 before v3.8.0 might allow a remote authenticated actor to achieve code execution in inference containers via replacement of model artifacts in S3 with a specially crafted pickle payload that is deserialized without verification. This issue requires a remote authenticated actor with S3 write access to the model artifact path.

To remediate this issue, we recommend upgrading to Amazon SageMaker Python SDK v2.257.2 or v3.8.0 and rebuild any Triton models previously created with ModelBuilder using the updated SDK.

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

## Which versions are affected by CVE-2026-8597?

5 open source packages ship an affected version, including sagemaker.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sagemaker` | PyPI | From 2.199.0 | 2.257.2, 3.8.0 |
| `sagemaker` | PyPI | From 2.199.0 | 2.257.2 |
| `sagemaker` | PyPI | From 2.199.0 | 2.257.2 |
| `sagemaker` | PyPI | From 3.0.0 | 3.8.0 |
| `sagemaker` | PyPI | From 3.0.0 | 3.8.0 |

## How do I fix CVE-2026-8597?

Upgrade sagemaker to a fixed version for your release line: 2.257.2 or 3.8.0.

## Is CVE-2026-8597 being exploited?

There is no known exploitation of CVE-2026-8597 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8597 and fix it if it is affected.

What it is: CVE-2026-8597 is a medium-severity unsafe deserialization vulnerability in AWS Amazon SageMaker Python SDK, published on 14 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8597 in the wild and no public exploit code.

Affected packages and fixed versions:
- sagemaker (PyPI): affected from 2.199.0; fixed in 2.257.2, 3.8.0
- sagemaker (PyPI): affected from 2.199.0; fixed in 2.257.2
- sagemaker (PyPI): affected from 2.199.0; fixed in 2.257.2
- sagemaker (PyPI): affected from 3.0.0; fixed in 3.8.0
- sagemaker (PyPI): affected from 3.0.0; fixed in 3.8.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8597/ (Markdown: https://insights.sbomify.com/CVE-2026-8597/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8597
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8597
- OSV: https://osv.dev/vulnerability/CVE-2026-8597

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8597/
Summaries are generated and may contain mistakes; the official description above is the record.