VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

sagemaker: vulnerability history, versions and safety

sagemaker is a package in the PyPI ecosystem. Vulert records 15 vulnerabilities for it across 96 releases, from May 2024 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
15 vulnerabilities recorded H6 M2 U7
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
12 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sagemaker vulnerabilities

Vulert verdict on sagemaker 3.27.0 i

Updated on 23 Oct 2026

Good news: 3.27.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 15.

Package health score 67/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 3.27.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.27.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.27.0 — unaffected i
  • Vulnerabilities on record 15 over 2 years · 12 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 0 i
  • Stars 2,269 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for sagemaker, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.27.0 21 Oct 2026 none non-standard — Details →
3.26.0 20 Oct 2026 none non-standard — Details →
3.25.0 14 Oct 2026 none non-standard — Details →
2.257.7 07 Oct 2026 H1 non-standard Yes Details →
3.24.0 07 Oct 2026 none non-standard — Details →
3.23.0 24 Sep 2026 none non-standard — Details →
3.22.1 18 Sep 2026 none non-standard — Details →
3.22.0 15 Sep 2026 none non-standard — Details →
3.21.0 25 Aug 2026 none non-standard — Details →
3.20.0 14 Aug 2026 none non-standard — Details →
3.19.0 11 Aug 2026 none non-standard — Details →
2.257.6 10 Aug 2026 H1 non-standard Yes Details →
3.18.0 30 Jul 2026 none non-standard — Details →
3.17.0 25 Jul 2026 none non-standard — Details →
3.16.0 16 Jul 2026 none non-standard — Details →
2.257.5 14 Jul 2026 H1 non-standard Yes Details →
2.257.4 14 Jul 2026 H1 non-standard Yes Details →
3.15.1 14 Jul 2026 none non-standard — Details →
3.15.0 27 Jun 2026 none non-standard — Details →
3.14.0 19 Jun 2026 none non-standard — Details →
3.13.1 05 Jun 2026 none non-standard — Details →
3.13.0 03 Jun 2026 none non-standard — Details →
3.12.0 20 May 2026 none non-standard — Details →
3.11.0 13 May 2026 none non-standard — Details →
3.10.1 08 May 2026 none non-standard — Details →
2.257.3 04 May 2026 H1 non-standard Yes Details →
3.10.0 02 May 2026 none non-standard — Details →
3.9.0 23 Apr 2026 none non-standard — Details →
2.257.2 20 Apr 2026 H1 non-standard Yes Details →
3.8.0 16 Apr 2026 none non-standard — Details →
3.7.1 01 Apr 2026 U2 non-standard Yes Details →
3.7.0 25 Mar 2026 U2 non-standard Yes Details →
3.6.0 20 Mar 2026 U2 non-standard Yes Details →
2.257.1 05 Mar 2026 H2 M1 U2 non-standard Yes Details →
3.5.0 03 Mar 2026 U2 non-standard Yes Details →
3.4.1 11 Feb 2026 U2 non-standard Yes Details →
2.257.0 03 Feb 2026 H2 M1 U2 non-standard Yes Details →
3.4.0 23 Jan 2026 U2 non-standard Yes Details →
2.256.1 21 Jan 2026 H2 M1 U2 non-standard Yes Details →
3.3.1 13 Jan 2026 H1 U2 non-standard Yes Details →
2.256.0 08 Jan 2026 H2 M1 U2 non-standard Yes Details →
3.3.0 20 Dec 2025 H1 U2 non-standard Yes Details →
3.2.0 19 Dec 2025 H1 U2 non-standard Yes Details →
3.1.1 11 Dec 2025 H2 U3 non-standard Yes Details →
3.1.0 03 Dec 2025 H3 U4 non-standard Yes Details →
2.251.2.dev0 03 Dec 2025 H2 M1 U4 non-standard Yes Details →
2.255.0 03 Dec 2025 H2 M1 U4 non-standard Yes Details →
2.254.2.dev0 03 Dec 2025 H2 M1 U4 non-standard Yes Details →
3.0.1 20 Nov 2025 H3 U4 non-standard Yes Details →
3.0.0 20 Nov 2025 H3 non-standard Yes Details →
2.254.1 31 Oct 2025 H2 M1 U4 non-standard Yes Details →
2.254.0 29 Oct 2025 H2 M1 U4 non-standard Yes Details →
2.253.1 14 Oct 2025 H2 M1 U4 non-standard Yes Details →
2.253.0 10 Oct 2025 H2 M1 U4 non-standard Yes Details →
2.252.0 29 Sep 2025 H2 M1 U4 non-standard Yes Details →
2.251.1 29 Aug 2025 H2 M1 U4 non-standard Yes Details →
2.251.0 21 Aug 2025 H2 M1 U4 non-standard Yes Details →
2.250.0 08 Aug 2025 H2 M1 U4 non-standard Yes Details →
2.249.0 31 Jul 2025 H2 M1 U4 non-standard Yes Details →
2.248.2 22 Jul 2025 H2 M1 U4 non-standard Yes Details →
2.248.1 16 Jul 2025 H2 M1 U4 non-standard Yes Details →
2.248.0 15 Jul 2025 H2 M1 U4 non-standard Yes Details →
2.247.1 23 Jun 2025 H2 M1 U4 non-standard Yes Details →
2.247.0 13 Jun 2025 H2 M1 U4 non-standard Yes Details →
2.246.0 04 Jun 2025 H2 M1 U4 non-standard Yes Details →
2.245.0 28 May 2025 H2 M1 U4 non-standard Yes Details →
2.244.2 19 May 2025 H2 M1 U4 non-standard Yes Details →
2.244.1 15 May 2025 H2 M1 U4 non-standard Yes Details →
2.243.4 07 May 2025 H2 M1 U4 non-standard Yes Details →
2.244.0 02 May 2025 H2 M1 U4 non-standard Yes Details →
2.243.3 23 Apr 2025 H2 M1 U4 non-standard Yes Details →
2.243.2 16 Apr 2025 H2 M1 U4 non-standard Yes Details →
2.243.1 11 Apr 2025 H2 M1 U4 non-standard Yes Details →
2.243.0 27 Mar 2025 H2 M1 U4 non-standard Yes Details →
2.242.0 14 Mar 2025 H2 M1 U4 non-standard Yes Details →
2.241.0 06 Mar 2025 H2 M1 U4 non-standard Yes Details →
2.240.0 25 Feb 2025 H2 M1 U4 non-standard Yes Details →
2.239.3 19 Feb 2025 H2 M1 U4 non-standard Yes Details →
2.239.2 18 Feb 2025 H2 M1 U4 non-standard Yes Details →
2.239.1 14 Feb 2025 H2 M1 U4 non-standard Yes Details →
2.239.0 01 Feb 2025 H2 M1 U4 non-standard Yes Details →
2.238.0 29 Jan 2025 H2 M1 U4 non-standard Yes Details →
2.237.3 09 Jan 2025 H2 M1 U4 non-standard Yes Details →
2.237.1 12 Dec 2024 H2 M2 U5 non-standard Yes Details →
2.237.0 05 Dec 2024 H2 M2 U5 non-standard Yes Details →
2.236.0 04 Dec 2024 H2 M2 U5 non-standard Yes Details →
2.235.2 22 Nov 2024 H2 M2 U5 non-standard Yes Details →
2.235.1 20 Nov 2024 H2 M2 U5 non-standard Yes Details →
2.235.0 19 Nov 2024 H2 M2 U5 non-standard Yes Details →
2.234.0 19 Nov 2024 H2 M2 U5 non-standard Yes Details →
2.233.0 04 Nov 2024 H2 M2 U5 non-standard Yes Details →
2.232.3 30 Oct 2024 H2 M2 U5 non-standard Yes Details →
2.232.2 03 Oct 2024 H2 M2 U5 non-standard Yes Details →
2.232.1 19 Sep 2024 H2 M2 U5 non-standard Yes Details →
2.232.0 12 Sep 2024 H2 M2 U5 non-standard Yes Details →
2.231.0 30 Aug 2024 H2 M2 U5 non-standard Yes Details →
2.230.0 28 Aug 2024 H2 M2 U5 non-standard Yes Details →
2.229.0 15 Aug 2024 H2 M2 U5 — Yes Details →
2.228.0 06 Aug 2024 H2 M2 U5 — Yes Details →
2.227.0 30 Jul 2024 H2 M2 U5 Apache-2.0 Yes Details →
2.226.1 17 Jul 2024 H2 M2 U5 — Yes Details →
2.226.0 12 Jul 2024 H2 M2 U5 — Yes Details →
2.225.0 10 Jul 2024 H2 M2 U5 — Yes Details →
2.224.4 04 Jul 2024 H2 M2 U5 — Yes Details →
2.224.3 03 Jul 2024 H2 M2 U5 — Yes Details →
2.224.2 27 Jun 2024 H2 M2 U5 — Yes Details →
2.224.1 21 Jun 2024 H2 M2 U5 — Yes Details →
2.224.0 19 Jun 2024 H2 M2 U5 — Yes Details →
2.223.0 13 Jun 2024 H2 M2 U5 — Yes Details →
2.222.1 12 Jun 2024 H2 M2 U5 — Yes Details →
2.222.0 07 Jun 2024 H2 M2 U5 — Yes Details →
2.221.1 22 May 2024 H2 M2 U5 — Yes Details →
2.221.0 20 May 2024 H2 M2 U5 — Yes Details →
2.220.0 15 May 2024 H2 M2 U5 — Yes Details →
2.219.0 08 May 2024 H2 M2 U5 — Yes Details →
2.218.1 03 May 2024 H2 M2 U5 — Yes Details →
2.218.0 01 May 2024 H2 M2 U5 — Yes Details →
2.217.0 24 Apr 2024 H3 M2 U6 — Yes Details →
2.216.1 22 Apr 2024 H3 M2 U6 — Yes Details →
2.216.0 17 Apr 2024 H3 M2 U6 — Yes Details →

The newest 120 of 697 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2
  • 2025 1
  • 2026 12

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 12 of the 15 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for sagemaker

The 5 most severe of 15 vulnerabilities recorded for this package

Search all 15 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
CVE-2024-34073: sagemaker-python-sdk Command Injection Vulnerability 7.8 high 2.214.3 07 Jul 2026
CVE-2024-34072: sagemaker-python-sdk Vulnerable to Deserialization of Untrusted Data 7.8 high 2.218.0 07 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About sagemaker

Is sagemaker safe to use?

Vulert records 15 vulnerabilities for sagemaker in PyPI: 0 critical, 6 high, 2 medium and 0 low, plus 7 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is sagemaker's Vulert package health score?

Vulert scores sagemaker 67/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of sagemaker affected?

No. 3.27.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does sagemaker have?

15 vulnerabilities are recorded for sagemaker in the PyPI ecosystem: 0 critical, 6 high, 2 medium and 0 low, plus 7 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new sagemaker vulnerabilities disclosed?

12 vulnerabilities were recorded for sagemaker in the last 12 months, and the oldest entry in this database dates to 03 May 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of sagemaker are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.