---
id: "CVE-2026-110248"
kind: "vulnerability"
aliases: ["CVE-2026-110248"]
title: "Amazon SageMaker Python SDK: failed Git clones log repository credentials in plaintext"
severity: "medium"
cvss: 6.0
epss: 0.00531
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["aws", "cloudwatch", "lab-disclosure", "package", "python", "sagemaker"]
not_affected_if: ["fixed-version", "no-credentials-in-url", "no-git-clone"]
published_at: "2026-10-14T00:00:00+00:00"
first_seen_at: "2026-10-24T20:05:36+00:00"
updated_at: "2026-10-25T12:38:49+00:00"
sources: [{"source": "lab", "url": "https://aws.amazon.com/security/security-bulletins/rss/2026-134-aws/", "first_seen_at": "2026-10-24T20:05:36+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-110248", "first_seen_at": "2026-10-24T20:15:27+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-110248", "first_seen_at": "2026-10-25T12:38:49+00:00"}]
---

# Amazon SageMaker Python SDK: failed Git clones log repository credentials in plaintext

When 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, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `pip show sagemaker` to see the installed version of the SageMaker Python SDK, and compare it with the fixed releases.
- Search CloudWatch Logs for SageMaker jobs with Git clone failures, and look for credentials embedded in repository URLs.
- Check whether repository URLs used by SageMaker jobs contain usernames, tokens or passwords.

## Fix

- Upgrade the SageMaker Python SDK V2 to `2.257.3` or later, or V3 to `3.10.0` or later.
- Rotate any credentials that appeared in CloudWatch Logs output from failed Git clone operations.
- Stop putting credentials in Git repository URLs and use a secrets mechanism instead.
- Restrict access to CloudWatch Logs that contain SageMaker SDK output.

## Timeline

- 2026-10-24T20:05:36+00:00 lab https://aws.amazon.com/security/security-bulletins/rss/2026-134-aws/ — AWS: CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK
- 2026-10-24T20:15:27+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-110248
- 2026-10-25T12:38:49+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-110248

## Documents

- [advisory] AWS: CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK https://aws.amazon.com/security/security-bulletins/rss/2026-134-aws/

## From the sources

CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK

### 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:

- Amazon SageMaker Python SDK V2 versions before 2.257.3
- Amazon SageMaker Python SDK V3 versions before 3.10.0

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:

- CVE-2026-110248
- GHSA-g6w4-jvgp-68x2

Acknowledgement:

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

 Please email aws-security@amazon.com with any security questions or concerns.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_