SageMaker Workflow component allows possibility of MD5 hash collisions

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2025-0508: 0.27% estimated exploitation activity in the next 30 days; percentile 18.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability in the SageMaker Workflow component of aws/sagemaker-python-sdk allows for the possibility of MD5 hash collisions in all versions. This can lead to workflows being inadvertently replaced due to the reuse of results from different configurations that produce the same MD5 hash. This issue can cause integrity problems within the pipeline, potentially leading to erroneous processing outcomes.

Published by the source

20 Mar 2025, 12:32 UTC

Last modified by the source

7 Jul 2026, 17:56 UTC

Source last checked

26 Oct 2026, 13:35 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-32g6-mg92-ghm2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-32g6-mg92-ghm2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-0508

Advisory: SageMaker Workflow component allows possibility of MD5 hash collisions
IDs: CVE-2025-0508, GHSA-32g6-mg92-ghm2
Record: https://patchnext.com/advisories/cve-2025-0508 (revision 2, source checked 26 Oct 2026, 13:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sagemaker 2.237.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI sagemaker: affected < 2.237.3; fixed in 2.237.3

## Suggested inspection (read-only)
- `python -m pip show sagemaker`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sagemaker.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-32g6-mg92-ghm2 (OSV record GHSA-32g6-mg92-ghm2 lists affected ranges: PyPI sagemaker >=0 <2.237.3 (fixed))
- Verified: https://github.com/advisories/GHSA-32g6-mg92-ghm2 (GitHub-reviewed advisory GHSA-32g6-mg92-ghm2 lists affected ranges: PyPI sagemaker >=0 <2.237.3)

Commands are suggestions: review each one before running it.