Vulnerability Database · PyPI · sagemaker · Version
sagemaker 3.0.0
3.0.0 is affected by 3 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 3 Medium 0 Low 0 Unrated 0
-
Released 20 Nov 2025
Licence non-standard
Also known from other sources 9
Newer releases 300
Database updated 23/Oct/2026
Release and licence data published by PyPI. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
sagemaker 3.0.0 vulnerabilities
3 vulnerabilities cover sagemaker 3.0.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-1777: SageMaker Python SDK HMAC Exposure Vulnerability | 8.7 high | 3.2.0 | 02 Feb 2026 |
| CVE-2026-1778: SageMaker Python SDK Insecure TLS Configuration Vulnerability | 8.7 high | 3.1.1 | 02 Feb 2026 |
| Critical Security Flaw in SageMaker Python SDK: Remote Code Execution Risk | 8.4 high | 3.4.0 | 05 Mar 2026 |
Looking for another version, or everything Vulert holds for sagemaker?
Questions
About sagemaker 3.0.0
Is sagemaker 3.0.0 vulnerable?
Yes. 3 vulnerabilities in the Vulert database cover sagemaker 3.0.0: 0 critical, 3 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 3.0.0 the latest release of sagemaker?
No. 3.0.0 was published 20 Nov 2025, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor sagemaker for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the sagemaker version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.