Every CVE Search/ Get API key

CVE-2026-1778

TLS disabled by default in select aws/sagemaker-python-sdk configurations

8.2 HighFix available

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.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
Low
Privileges needed
None
User interaction
None

What an attacker can affect

Confidentiality
None
Integrity
High
Availability
None

Exploit likelihood

0.26%Up 0.3 points since Feb 3, 2026
90%50%10%1%

What each source reports

CVE List Score used 8.2

TLS disabled by default in select aws/sagemaker-python-sdk configurations

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.

Record
CVE-2026-1778
CVSS 4.0
8.2 HighCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
CVSS 3.1
5.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness
CWE-295
Updated
2026-11-02
EUVDEUVD-2026-5266 8.2

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.

Record
EUVD-2026-5266
CVSS 4.0
8.2 HighCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Updated
2026-11-02
GitHub AdvisoriesGHSA-62rc-f4v9-h543 8.7

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

  • 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]. Please do not create a public GitHub issue.

Record
GHSA-62rc-f4v9-h543
CVSS 4.0
8.7 HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CVSS 3.1
5.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness
CWE-295, CWE-599
Updated
2026-11-02
NVD 8.2

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.

Record
CVE-2026-1778
CVSS 4.0
8.2 HighCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS 3.1
5.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness
CWE-295
Updated
2026-11-02
OSV 8.2

TLS disabled by default in select aws/sagemaker-python-sdk configurations

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.

Record
CVE-2026-1778
CVSS 4.0
8.2 HighCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Weakness
CWE-295
Updated
2026-11-02
OSVGHSA-62rc-f4v9-h543 8.7

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

  • 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]. Please do not create a public GitHub issue.

Record
GHSA-62rc-f4v9-h543
CVSS 4.0
8.7 HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CVSS 3.1
5.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Weakness
CWE-295, CWE-599
Updated
2026-11-02
OSVPYSEC-2026-1886 8.7

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

  • 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]. Please do not create a public GitHub issue.

Record
PYSEC-2026-1886
CVSS 4.0
8.7 HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CVSS 3.1
5.9 MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
sagemaker
PyPI
 3.0 up to 3.1.1
3.1.1
sagemaker
PyPI
 before 2.256.0
2.256.0
sagemaker
PyPI
 3.0 up to 3.1.1, plus listed versions
3.0.13.1.0
3.1.1
sagemaker
PyPI
 before 2.256.0, plus listed versions
1.0.01.0.11.0.21.1.01.1.1
Show 45 moreShow less
1.1.21.1.31.10.01.10.11.11.01.11.11.11.21.11.31.12.01.13.01.14.01.14.11.14.21.15.01.15.11.15.21.16.11.16.1.post11.16.21.16.31.17.01.17.11.17.21.18.01.18.11.18.101.18.111.18.121.18.131.18.141.18.14.post01.18.14.post11.18.151.18.161.18.171.18.181.18.191.18.21.18.31.18.3.post11.18.41.18.51.18.6.post01.18.71.18.8
2.256.0
sagemaker
PyPI
 before 2.256.0, 3.0 up to 3.1.1, plus listed versions
1.0.01.0.11.0.21.1.01.1.1
Show 45 moreShow less
1.1.21.1.31.10.01.10.11.11.01.11.11.11.21.11.31.12.01.13.01.14.01.14.11.14.21.15.01.15.11.15.21.16.11.16.1.post11.16.21.16.31.17.01.17.11.17.21.18.01.18.11.18.101.18.111.18.121.18.131.18.141.18.14.post01.18.14.post11.18.151.18.161.18.171.18.181.18.191.18.21.18.31.18.3.post11.18.41.18.51.18.6.post01.18.71.18.8
2.256.03.1.1

History

History
RecordedChangedSources
first indexedCVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2026-1778 is a high vulnerability (CVSS 8.2) in Aws Sagemaker Python Sdk, published February 2, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.26%, the 17th percentile. Fixed in sagemaker 3.1.1.

References

Show 5 moreShow less
This page doesn't list everything

Left out here: 1,202 versions. The JSON record has them.

Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open