Live › vulnerability › CVE-2026-110248
Go to dashboardWhen a Git clone performed by the SageMaker Python SDK fails, the repository credentials appear in the subprocess error output and get written to CloudWatch Logs without redaction. Anyone with read access to those logs can recover the plaintext credentials.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-24 20:05 UTC, 0h before NVD. All times on this page are UTC.
Teams that run SageMaker jobs or notebooks that clone private Git repositories with the SageMaker Python SDK are exposed, most of all if credentials are embedded in the repository URL. Exposure also depends on who can read the CloudWatch Logs for those jobs. Teams on versions at or above the fixed releases, or whose SDK never performs Git clones, can skip it.
No product ranges from the sources yet.
pip show sagemaker to see the installed version of the SageMaker Python SDK, and compare it with the fixed releases.2.257.3 or later, or V3 to 3.10.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK
Bulletin ID: 2026-134-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/14/2026 11:30 AM PDT
Description:
Amazon SageMaker Python SDK is an open source library for training and deploying machine learning models on Amazon SageMaker.
We identified CVE-2026-110248, an issue in the git_utils.py component of Amazon SageMaker Python SDK. When a Git clone operation fails, repository credentials in subprocess error output are written to CloudWatch Logs without redaction. An authenticated remote user with access to those logs is able to obtain the plaintext credentials.
Impacted versions:
Resolution:
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 incorporates the fixes.
Workarounds:
If immediate upgrading is not possible, 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 were present in the affected log output.
References:
Acknowledgement:
We would like to thank Gouri Sankar A for collaborating on this issue through the coordinated vulnerability disclosure process.
Please email [email protected] with any security questions or concerns.
This page as .md · .json · in your agent: get_signal("CVE-2026-110248")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.