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, facilitating model training, deployment, and management. However, a critical vulnerability has been identified in the SDK related to its handling of SSL certificate verification, which can expose users to significant security risks.
Vulnerability Detail
The vulnerability arises from the global disabling of SSL certificate verification in the Triton Python backend of the SageMaker Python SDK. This insecure configuration allows malicious actors to intercept HTTPS traffic, potentially replacing models or dependencies with compromised versions. Such an attack could lead to arbitrary code execution within the Triton container, posing severe risks to the integrity and security of applications utilizing the 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 advisable to add the private Certificate Authority (CA) certificate to the container image. This approach ensures secure operations while accommodating trusted internal domains. Here’s a sample command to add a CA certificate:
COPY your-ca.crt /usr/local/share/ca-certificates/your-ca.crt
RUN update-ca-certificates
Conclusion
The SageMaker Python SDK has a critical vulnerability due to insecure TLS configuration, allowing for potential remote code execution. Users are strongly advised to upgrade to the latest patched versions and implement recommended workarounds to mitigate risks. Regular monitoring for vulnerabilities using tools like Vulert can enhance security.
See every vulnerability recorded for sagemaker →
FAQ
The vulnerability involves the disabling of SSL certificate verification, which can lead to interception of HTTPS traffic and potential remote code execution.
The affected versions are SageMaker Python SDK v3 < v3.1.1 and v2 < v2.256.0.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
As a temporary measure, consider using self-signed certificates and adding your private CA certificate to the container image to maintain security.
The consequences include the risk of arbitrary code execution, which can compromise the security and integrity of applications using the SDK.
References
Related vulnerabilities
Recent vulnerabilities recorded for sagemaker.
