sagemaker
Affected
- introduced
3.0, fixed3.1.1(ecosystem)
Fixed versions
3.1.1
Fix
- Fixed version
3.1.1pip install --upgrade sagemaker==3.1.1
Advisory
Also known as: CVE-2026-1778, PYSEC-2026-1886
SageMaker Python SDK has Insecure TLS Configuration
Summary
SageMaker Python SDK is an open source library for training and deploying machine learning models on Amazon SageMaker. An issue where SSL certificate verification was globally disabled in the Triton Python backend has been found.
Impact
Arbitrary Code Execution: Disabling SSL verification allows third parties to intercept HTTPS traffic and replace models or dependencies with inappropriate versions. This could lead to remote code execution in the Triton container.
Impacted versions
Patches
This issue has been addressed in SageMaker Python SDK version v3.1.1 and v2.256.0. It is recommended to upgrade to the latest version immediately and ensure any forked or derivative code is patched to incorporate the new fixes.
Workarounds
Customers using self-signed certificates for internal model downloads should add their private Certificate Authority (CA) certificate to the container image rather than relying on the SDK’s previous insecure configuration. This opt-in approach maintains security while accommodating internal trusted domains.
References
If there are any questions or comments about this advisory, contact AWS Security via the vulnerability reporting page or directly via email to [[email protected]](mailto:[email protected]). Please do not create a public GitHub issue.
High Basis: The source's own band: HIGH
3.0, fixed 3.1.1 (ecosystem)3.1.1
3.1.1pip install --upgrade sagemaker==3.1.10, fixed 2.256.0 (ecosystem)2.256.0
2.256.0pip install --upgrade sagemaker==2.256.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0