CVE-2026-1778: SageMaker Python SDK Insecure TLS Configuration Vulnerability
Summary
CVE-2026-1778: SageMaker Python SDK has Insecure TLS Configuration. Affects sagemaker across 2 version ranges.
< 2.256.0
>= 3.0, < 3.1.1
Fixed in 2.256.0 or 3.1.1, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The SageMaker Python SDK is an open-source library designed for training and deploying machine learning models on Amazon SageMaker. It provides a user-friendly interface for developers to interact with SageMaker services, enabling efficient model management and deployment. However, a critical vulnerability has been identified that compromises the security of SSL certificate verification within the Triton Python backend.
Vulnerability Detail
The vulnerability arises from the global disabling of SSL certificate verification in the Triton Python backend of the SageMaker Python SDK. This flaw allows malicious actors to intercept HTTPS traffic, potentially replacing models or dependencies with unauthorized versions. The consequences of this vulnerability include the risk of arbitrary code execution within the Triton container, posing significant security threats to applications relying on this SDK.
How To Fix
Latest published version: 3.27.0 as of 22 Oct 2026
pip install --upgrade "sagemaker==3.27.0"Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 2.256.02.256.0pip install --upgrade "sagemaker==2.256.0" -
>= 3.0, < 3.1.13.1.1pip install --upgrade "sagemaker==3.1.1"
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
For users relying on self-signed certificates for internal model downloads, it is recommended to add the private Certificate Authority (CA) certificate to the container image. This approach maintains security while accommodating trusted internal domains. Users can include their CA certificate in the Dockerfile as follows:
COPY path/to/your/ca.crt /usr/local/share/ca-certificates/
RUN update-ca-certificates
Conclusion
In summary, the SageMaker Python SDK has a critical vulnerability due to insecure TLS configuration that can lead to severe security risks, including arbitrary code execution. Users are strongly advised to upgrade to the latest patched versions or implement workarounds to mitigate the risks associated with this vulnerability.
See every vulnerability recorded for sagemaker →
FAQ
The vulnerability involves the disabling of SSL certificate verification, which can lead to arbitrary code execution.
SageMaker Python SDK versions prior to 3.1.1 for v3 and prior to 2.256.0 for v2 are affected.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If immediate upgrading is not possible, consider implementing the recommended workaround by adding your CA certificate to the container image.
The CVSS score of this vulnerability is 8.7, indicating a high severity level.
References
Related vulnerabilities
Recent vulnerabilities recorded for sagemaker.
