CVE-2026-1778: PYSEC-2026-1886 - SageMaker Python SDK has Insecure TLS Configuration

CVE-2026-1778 · Severity: low · CVSS 3.1 · Published 2026-07-07

SageMaker Python SDK has Insecure TLS Configuration

Technologies: sagemaker (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-1778 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-1778 being exploited in the wild.
How severe is CVE-2026-1778?
Low severity, with a CVSS score of 3.1, published 7 July 2026.
Which products and versions are affected?
sagemaker (PyPI) ECOSYSTEM:introduced=0,fixed=2.256.0,introduced=3.0,fixed=3.1.1, ECOSYSTEM:introduced=3.0,fixed=3.1.1.
Is there a fix for CVE-2026-1778?
Yes. sagemaker (PyPI): upgrade to 3.1.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-1778?
Check whether you run sagemaker (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • sagemaker (PyPI): upgrade to 3.1.1 or later
    pip install "sagemaker>=3.1.1"

Affected products

  • sagemaker (PyPI) ECOSYSTEM:introduced=0,fixed=2.256.0,introduced=3.0,fixed=3.1.1, ECOSYSTEM:introduced=3.0,fixed=3.1.1

Identifiers

  • CVE-2026-1778
  • GHSA-62rc-f4v9-h543
  • PYSEC-2026-1886

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.