https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-03T06:06:52.239824+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cve-2026-1778 CVE-2026-1778 — TLS disabled by default in select aws/sagemaker-python-sdk configurations 2026-10-03T06:06:52.255793+00:00

Affected: AWS SageMaker Python SDK

Amazon SageMaker Python SDK before v3.1.1 or v2.256.0 disables TLS certificate verification for HTTPS connections made by the service when a Triton Python model is imported, incorrectly allowing for requests with invalid and self-signed certificates to succeed.

 https://cve.radiocsirt.org/vuln/ghsa-62rc-f4v9-h543 GHSA-62rc-f4v9-h543 — SageMaker Python SDK has Insecure TLS Configuration 2026-10-03T06:06:52.255847+00:00

Affected: PyPI: sagemaker

### 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](https://github.com/aws/sagemaker-python-sdk/tree/1ab6d30401946e92fdbea18497675681649e0153) and [v2.256.0](https://github.com/aws/sagemaker-python-sdk/tree/a140cfcd12abfee10254cb4dea3bb10758e4321c). 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](https://aws.amazon.com/securi…