CVE-2026-8597

Amazon SageMaker Python SDK is an open-source library for training and deploying machine learning models on Amazon SageMaker. An issue exists where, under certain circumstances, the Triton inference handler deserializes model artifacts without performing integrity verification, allowing specially crafted pickle payloads to execute arbitrary code.

Workarounds

If upgrading is not immediately possible, users should restrict S3 write access to model artifact paths to only trusted principals and monitor for unintended modifications to files in model artifact S3 locations.

References

If there any questions or comments about this advisory, contact AWS Security via vulnerability reporting page or directly via email to [email protected]. Please do not create a public GitHub issue.

When using ModelBuilder with the Triton inference server, the Triton handler did not perform integrity verification before deserializing model artifacts. A remote authenticated actor with S3 write access to the model artifact path could replace model files with a crafted payload that would execute automatically on the next container lifecycle event, achieving code execution with the SageMaker execution role's IAM permissions.

Impacted versions: >= v2.199.0 AND <= v2.257.1, >= v3.0.0 AND <= v3.7.1

CVE-2026-8597 has a CVSS score of 7.2 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.257.2, 3.8.0); upgrading removes the vulnerable code path.

Kodem intelligence

This issue has been addressed in Amazon SageMaker Python SDK v2.257.2 and v3.8.0. The Triton inference handler now performs integrity verification before deserializing model artifacts. AWS recommend upgrading to the latest version and rebuilding any Triton models previously created with ModelBuilder using the updated SDK. Ensure any forked or derivative code is patched to incorporate the new fixes.

1. What is CVE-2026-8597? CVE-2026-8597 is a medium-severity security vulnerability in sagemaker (pip), affecting versions >= 2.199.0, <= 2.257.1. It is fixed in 2.257.2, 3.8.0.
2. How severe is CVE-2026-8597? CVE-2026-8597 has a CVSS score of 7.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of sagemaker are affected by CVE-2026-8597? sagemaker (pip) versions >= 2.199.0, <= 2.257.1 is affected.
4. Is there a fix for CVE-2026-8597? Yes. CVE-2026-8597 is fixed in 2.257.2, 3.8.0. Upgrade to this version or later.
5. Is CVE-2026-8597 exploitable, and should I be worried? Whether CVE-2026-8597 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-8597 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-8597?
   • Upgrade sagemaker to 2.257.2 or later
   • Upgrade sagemaker to 3.8.0 or later