CVE-2026-8597 json
Missing integrity verification in Triton inference handler in Amazon SageMaker Python SDK
published 5mo ago modified 16d ago also EUVD-2026-30423 , GHSA-rq6v-x3j8-7qgf , PYSEC-2026-3060
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi sagemaker 2.257.2, 3.8.0
Is CVE-2026-8597 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 5mo ago
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 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 |
| GitHub | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| OSV | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | sagemaker | >=2.199.0, <2.257.2 >=3.0.0, <3.8.0 |
2.257.2 3.8.0 |
Affected products
- AWS Amazon SageMaker Python SDK
Classification
- Weakness
-
- CWE-354 Improper Validation of Integrity Check Value
References
-
github.com
/aws/sagemaker-python-sdk/releases/tag/v2.257.2
patch, web
-
github.com
/aws/sagemaker-python-sdk/releases/tag/v3.8.0
patch, web
-
aws.amazon.com
/security/security-bulletins/2026-031-aws/
vendor-advisory
-
github.com
/aws/sagemaker-python-sdk/security/advisories/GHSA-rq6v-x3j8-7qgf
third-party-advisory, web, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-8597
advisory
-
aws.amazon.com
/security/security-bulletins/2026-031-aws
web
-
github.com
/aws/sagemaker-python-sdk
package
-
pypi.org
/project/sagemaker
package
-
github.com
/advisories/GHSA-rq6v-x3j8-7qgf
advisory
Sources
- CVE List CVE-2026-8597
- GitHub Advisory GHSA-rq6v-x3j8-7qgf
- NVD CVE-2026-8597
- OSV PYSEC-2026-3060
- Maintainer advisory GHSA-rq6v-x3j8-7qgf
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of aws/sagemaker-python-sdk published their own advisory on GitHub. Reviewed sources take precedence over it.