CVE-2024-34072: PYSEC-2026-1889 - sagemaker-python-sdk vulnerable to Deserialization of Untrusted Data

CVE-2024-34072 · Severity: low · CVSS 3.1 · Published 2026-07-07

sagemaker-python-sdk vulnerable to Deserialization of Untrusted Data

Technologies: sagemaker (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2024-34072 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-34072 being exploited in the wild.
How severe is CVE-2024-34072?
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.218.0.
Is there a fix for CVE-2024-34072?
Yes. sagemaker (PyPI): upgrade to 2.218.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-34072?
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 2.218.0 or later
    pip install "sagemaker>=2.218.0"

Affected products

  • sagemaker (PyPI) ECOSYSTEM:introduced=0,fixed=2.218.0

Identifiers

  • CVE-2024-34072
  • GHSA-wjvx-jhpj-r54r
  • PYSEC-2026-1889

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