Skip to content

Repository navigation

Insertion of sensitive information into log files in Amazon SageMaker Python SDK git_utils.py

Moderate
lucasjia-aws published GHSA-g6w4-jvgp-68x2 Oct 14, 2026

Package

pip sagemaker (pip)

Affected versions

<2.257.3
>= 3.0.0, < 3.10.0

Patched versions

2.257.3
3.10.0

Description

Summary

Amazon SageMaker Python SDK is an open source library for training and deploying machine learning models on Amazon SageMaker. An issue exists where repository credentials are included in log output when a Git clone operation fails.

Impact

The _runclone_command() function in the git_utils.py component does not redact repository credentials from subprocess error output. When a Git clone operation fails, plaintext credentials might be written to CloudWatch Logs. An authenticated remote user with access to those logs is able to obtain the credentials.

Impacted versions:

  • Amazon SageMaker Python SDK V2 versions before 2.257.3
  • Amazon SageMaker Python SDK V3 versions from 3.0.0 through 3.9.x

Patches

This issue has been addressed in Amazon SageMaker Python SDK V2 version 2.257.3 and V3 version 3.10.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the fixes.

Workarounds

If immediate upgrading is not possible, avoid including credentials in Git repository URLs and restrict access to CloudWatch Logs containing Amazon SageMaker Python SDK output. Review logs from failed Git clone operations and rotate any credentials that were present in the affected log output.

References

If you have any questions or comments about this advisory, we ask that you contact AWS Security through our vulnerability reporting page at https://aws.amazon.com/security/vulnerability-reporting/ or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.

Acknowledgement

We would like to thank Gouri Sankar A for collaborating on this issue through the coordinated vulnerability disclosure process.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

CVE ID

CVE-2026-110248

Weaknesses

Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file. Learn more on MITRE.