Quick answers
- Is CVE-2025-0508 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-0508 being exploited in the wild.
- How severe is CVE-2025-0508?
- Low severity, with a CVSS score of 3, published 7 July 2026.
- Which products and versions are affected?
- sagemaker (PyPI) ECOSYSTEM:introduced=0,fixed=2.237.3.
- Is there a fix for CVE-2025-0508?
- Yes. sagemaker (PyPI): upgrade to 2.237.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-0508 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-0508?
- 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.237.3 or later
pip install "sagemaker>=2.237.3"
Technical details
The vulnerability is a weak cryptographic hash function issue (CWE-328, CWE-440) in the SageMaker Workflow component where MD5 is used for configuration fingerprinting and caching. MD5's collision resistance is broken, allowing two different workflow configurations to hash to the same value. This causes workflows to be inadvertently replaced or reused with incorrect parameters, compromising pipeline integrity. The attack requires only the ability to submit or modify workflow configurations—no authentication bypass or network exploit is needed. AWS has patched this in version 2.237.3 and later by replacing MD5 with SHA-256 for file hashing.
Affected products
- AWS SageMaker Python SDK all versions before 2.237.3
Identifiers
- CVE-2025-0508
- GHSA-32g6-mg92-ghm2
- PYSEC-2026-1885
Timeline
- 2025-03-20: disclosed: GHSA-32g6-mg92-ghm2 and CVE-2025-0508 published
- 2025-03-20: patched: Fix available in version 2.237.3 and later; commit dcdd99f replaces MD5 with SHA-256