Quick answers
- Is CVE-2026-110248 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110248 being exploited in the wild.
- How severe is CVE-2026-110248?
- High severity, with a CVSS score of 5.3, published 14 October 2026.
- Which products and versions are affected?
- Amazon SageMaker Python SDK V2 before 2.257.3, V3 before 3.10.0.
- Is there a fix for CVE-2026-110248?
- Yes: fixed in Amazon SageMaker Python SDK V2 2.257.3, V3 3.10.0. Until then: Avoid including credentials in Git repository URLs and restrict access to CloudWatch Logs containing SageMaker Python SDK output. Review logs from failed Git clone operations and rotate any credentials that appear in the affected log output. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110248 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-110248?
- Check whether you run Amazon AWS or Amazon SageMaker Python SDK 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
- Fixed in: Amazon SageMaker Python SDK V2 2.257.3, V3 3.10.0
Avoid including credentials in Git repository URLs and restrict access to CloudWatch Logs containing SageMaker Python SDK output. Review logs from failed Git clone operations and rotate any credentials that appear in the affected log output.
Technical details
The git_utils.py component fails to sanitize subprocess error output before logging to CloudWatch Logs, allowing repository credentials to be written in plaintext. The vulnerability requires an authenticated user with CloudWatch Logs read access and occurs when Git clone operations fail. An attacker can extract credentials from the unredacted error messages to compromise repository access.
Affected products
- Amazon SageMaker Python SDK V2 before 2.257.3, V3 before 3.10.0
Timeline
- 2026-10-14: disclosed
- 2026-10-14: patched