CVE-2026-110248: Insertion of sensitive information into log files in Amazon SageMaker Python SDK git_utils[.]py
Insertion of sensitive information into log files in the gitutils[.]py component in Amazon SageMaker Python SDK V3 before 3.10.0 and V2 before 2.257.3 might allow an authenticated remote user to obtain plaintext repository credentials from CloudWatch Logs when a git clone operation fails, because the runclonecommand() function does not redact credentials from subprocess error output.
To remediate this issue, users should upgrade to Amazon SageMaker Python SDK V3 3.10.0 or V2 2.257.3.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Amazon SageMaker Python SDK V3to a version that resolves this vulnerability.Fixed in 3.10.0 - Upgrade
Upgrade
Amazon SageMaker Python SDK V2to a version that resolves this vulnerability.Fixed in 2.257.3
Event History
Frequently Asked Questions
Who can access the exposed credentials?
An authenticated remote user who can obtain the relevant CloudWatch Logs may be able to recover plaintext repository credentials. Exposure occurs when a git clone operation fails and its subprocess error output is logged.
What conditions are required for exploitation?
The affected SDK must be used for a git clone operation that fails, and the clone error output must contain repository credentials. The attacker also needs authenticated access to the CloudWatch Logs containing that output.
Which versions should be upgraded?
Upgrade Amazon SageMaker Python SDK V3 to 3.10.0 or later, or V2 to 2.257.3 or later. Versions before those releases are affected.
How can I check for prior exposure?
Review CloudWatch Logs associated with failed git clone operations performed by affected SDK versions. Look for subprocess error output that may include plaintext repository credentials.