CVE-2026-1778
SageMaker Python SDK disables TLS verification during Triton import.
Is CVE-2026-1778 being exploited?
Not confirmed. CVE-2026-1778 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-1778?
CVE-2026-1778 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-1778?
Yes. A fix has been recorded for CVE-2026-1778. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-1778 affect?
CVE-2026-1778 affects Amazon SageMaker Python SDK (versions < 3.1.1), Amazon SageMaker Python SDK (versions < 2.256.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-1778?
Upgrade to 3.1.1+ or 2.256.0+ to restore TLS verification
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
MITM risk: attacker could intercept/alter HTTPS traffic from the SDK due to disabled TLS checks.
Patch when possible