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.
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 15 May 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 14 May 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Missing integrity verification in Triton inference handler in Amazon SageMaker Python SDK | |
| First Time appeared |
Amazon Sagemaker Python Sdk
Amazon Sagemaker Python Sdk aws |
|
| Weaknesses | CWE-354 | |
| CPEs | cpe:2.3:a:amazon_sagemaker_python_sdk:aws:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Amazon Sagemaker Python Sdk
Amazon Sagemaker Python Sdk aws |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: AMZN
Published:
Updated: 2026-05-15T13:30:22.628Z
Reserved: 2026-05-14T13:39:22.704Z
Link: CVE-2026-8597
Updated: 2026-05-15T13:30:17.059Z
Status : Awaiting Analysis
Published: 2026-05-14T20:17:21.340
Modified: 2026-05-15T14:10:31.000
Link: CVE-2026-8597
No data.
OpenCVE Enrichment
Updated: 2026-05-14T22:30:25Z