cve.bz

CVE-2026-8597 aws amazon sagemaker python sdk

6.4 mediumEPSS 0.5%Fix available

Medium (6.4) in aws amazon sagemaker python sdk. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in sagemaker 2.257.2, 3.8.0.

On this page
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.

Severity

CVSS 4.0

6.4 medium
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

CVSS 3.1

7.2 high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th percentile. Scored 2026-11-16. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-05-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-354 Improper Validation of Integrity Check Value
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • sagemaker (PyPI): fixed in 2.257.2, 3.8.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-8597 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-8597?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-8597?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-8597 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • aws:amazon sagemaker python sdk

Versions

From the CNA's record in the CVE List.

ProductAffected
AWS Amazon SageMaker Python SDKfrom 2.199.0 through 2.257.1
AWS Amazon SageMaker Python SDKfrom 3.0.0 through 3.7.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rq6v-x3j8-7qgfPyPIsagemaker>=2.199.0 <2.257.22.257.2
GHSA-rq6v-x3j8-7qgfPyPIsagemaker>=3.0.0 <3.8.03.8.0
PYSEC-2026-3060PyPIsagemaker>=2.199.0 <2.257.2
>=3.0.0 <3.8.0
2.257.2, 3.8.0

Attack patterns (CAPEC)

  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-145 Checksum Spoofing Severity: Medium
  • CAPEC-463 Padding Oracle Crypto Attack Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON