CVE-2026-1778: 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.
Published Feb 2, 2026 · Updated Feb 3, 2026
Affected packages
sagemaker
- Ecosystem
- PyPI
- Affected
- >= 3.0, < 3.1.1
- Fixed in
- 3.1.1
- Check
pip show sagemaker
sagemaker
- Ecosystem
- PyPI
- Affected
- < 2.256.0
- Fixed in
- 2.256.0
- Check
pip show sagemaker
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
- SageMaker Python SDK v3 < v3.1.1
- SageMaker Python SDK v2 < v2.256.0
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.
References
- https://github.com/aws/sagemaker-python-sdk/security/advisories/GHSA-62rc-f4v9-h543
- https://github.com/aws/sagemaker-python-sdk/commit/5e7a3efa7bec0a161194ffa0cef346dda93bf2c6
- https://github.com/aws/sagemaker-python-sdk/commit/c8098958910f7db78d07037425debfd4d44a6964
- https://github.com/aws/sagemaker-python-sdk/releases/tag/v2.256.0
- https://nvd.nist.gov/vuln/detail/CVE-2026-1778
- https://aws.amazon.com/security/security-bulletins/2026-004-AWS
- https://github.com/aws/sagemaker-python-sdk/releases/tag/v3.1.1
- https://github.com/advisories/GHSA-62rc-f4v9-h543
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-8596
Cleartext storage of HMAC signing key in Amazon SageMaker Python SDK ModelBuilder/Serve path
high7.2May 21, 2026CVE-2026-8597
Amazon SageMaker Python SDK is missing integrity verification in its Triton inference handler
medium7.2May 21, 2026GHSA-5r2p-pjr8-7fh7
SageMaker Python SDK replaced eval() with safe parser in JumpStart search functionality
high8.4Mar 5, 2026CVE-2026-1777
SageMaker Python SDK has Exposed HMAC
high7.2Feb 2, 2026CVE-2025-0508
SageMaker Workflow component allows possibility of MD5 hash collisions
medium5.9Mar 20, 2025CVE-2024-34072
sagemaker-python-sdk vulnerable to Deserialization of Untrusted Data
high7.8May 3, 2024
