{"id":"GHSA-g6w4-jvgp-68x2","kind":"vulnerability","aliases":["GHSA-g6w4-jvgp-68x2"],"related":[],"title":"CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK","description":"CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK\n\n### CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK\n\nBulletin ID: 2026-134-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/14/2026 11:30 AM PDT\n\nDescription:\n\nAmazon SageMaker Python SDK is an open source library for training and deploying machine learning models on Amazon SageMaker.\n\nWe 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.\n\nImpacted versions:\n\n- Amazon SageMaker Python SDK V2 versions before 2.257.3\n- Amazon SageMaker Python SDK V3 versions before 3.10.0\n\nResolution:\n\nThis 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.\n\nWorkarounds:\n\nIf 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.\n\nReferences:\n\n- CVE-2026-110248\n- GHSA-g6w4-jvgp-68x2\n\nAcknowledgement:\n\nWe would like to thank Gouri Sankar A for collaborating on this issue through the coordinated vulnerability disclosure process.\n\n Please email aws-security@amazon.com with any security questions or concerns.","summary":"When a Git clone fails inside the SageMaker Python SDK, the error output includes repository credentials, which are written to CloudWatch Logs without redaction. Anyone authenticated who can read those logs can recover the plaintext credentials.","severity":"medium","cvss":null,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["aws","lab-disclosure","ml-pipelines","package","python","sagemaker"],"not_affected_if":["no-credentials-in-git-urls","patched-version"],"how_to_check":"- Check the installed SDK version with `pip show sagemaker` and compare against `2.257.3` (V2) or `3.10.0` (V3).\n- Search CloudWatch Logs for SageMaker output from failed Git clone operations for embedded credentials in repository URLs.\n- Look for Git repository URLs that contain usernames, tokens or passwords in SageMaker job or pipeline definitions.","fix":"- Upgrade the SageMaker Python SDK V2 to `2.257.3` or V3 to `3.10.0`.\n- Ensure any forked or derivative code includes the fix.\n- Avoid putting credentials in Git repository URLs.\n- Rotate any credentials that appeared in affected CloudWatch log output.","status":"open","published_at":"2026-10-14T00:00:00+00:00","first_seen_at":"2026-10-24T20:05:36+00:00","triaged_at":"2026-10-25T05:27:51+00:00","updated_at":"2026-10-25T05:27:51+00:00","category":"package","confidence":0.7,"triage":{"at":"2026-10-25T05:27:51Z","model":"claude-haiku-5-5","output":{"fix":"- Upgrade the SageMaker Python SDK V2 to `2.257.3` or V3 to `3.10.0`.\n- Ensure any forked or derivative code includes the fix.\n- Avoid putting credentials in Git repository URLs.\n- Rotate any credentials that appeared in affected CloudWatch log output.","reach":"network","title":"Amazon SageMaker Python SDK: failed Git clones log repository credentials to CloudWatch","impact":"medium","summary":"When a Git clone fails inside the SageMaker Python SDK, the error output includes repository credentials, which are written to CloudWatch Logs without redaction. Anyone authenticated who can read those logs can recover the plaintext credentials.","category":"package","nicknames":[],"who_cares":["aws","sagemaker","python","ml-pipelines"],"confidence":0.7,"needs_auth":"yes","worst_case":"Repository credentials are read from CloudWatch Logs in plaintext","analyst_note":"","how_to_check":"- Check the installed SDK version with `pip show sagemaker` and compare against `2.257.3` (V2) or `3.10.0` (V3).\n- Search CloudWatch Logs for SageMaker output from failed Git clone operations for embedded credentials in repository URLs.\n- Look for Git repository URLs that contain usernames, tokens or passwords in SageMaker job or pipeline definitions.","needs_analyst":false,"not_affected_if":["patched-version","no-credentials-in-git-urls"],"who_is_affected":"Teams that run the SageMaker Python SDK to clone Git repositories during training or deployment and whose clone URLs carry credentials. Exposure also depends on who can read the CloudWatch log groups where that output lands. Teams on a patched version, or not using credentials in Git URLs, can skip it.","user_interaction":"no","needs_special_setup":"yes","severity_if_unknown":"medium"},"cost_usd":0.00073,"input_tokens":3943,"output_tokens":671,"severity_before":"unknown"},"analyst_status":null,"analyst_note":null,"search":"'-110248':3A,74C,89C,145C,292C '-134':105C '-2026':2A,73C,88C,144C,291C '10/14/2026':116C '11':117C '2.257.3':201C,223C '2026':104C '3.10.0':209C,227C '30':118C '68x2':20A,25A,297C 'abl':186C 'access':181C,261C 'acknowledg':298C 'address':215C 'affect':286C 'amazon':12A,83C,98C,122C,139C,153C,194C,202C,217C 'anyon':60B 'attent':113C 'authent':61B,177C 'avoid':252C 'aw':26B,106C,108C 'aws-security@amazon.com':320C 'bulletin':102C 'clone':39B,160C,275C 'cloudwatch':56B,172C,263C 'code':241C 'collabor':308C 'compon':151C 'concern':326C 'contain':265C 'content':109C 'coordin':314C 'credenti':51B,71B,164C,191C,254C,280C 'cve':1A,72C,87C,143C,290C 'date':115C 'deploy':134C 'deriv':240C 'descript':121C 'disclosur':29B,316C 'email':319C 'ensur':236C 'error':47B,167C 'fail':40B,162C,273C 'file':10A,81C,96C 'fix':244C 'fork':238C 'g6w4':18A,23A,295C 'ghsa':17A,22A,294C 'ghsa-g6w4-jvgp-68x2':16A,21A,293C 'git':38B,159C,256C,274C 'git_utils.py':150C 'gouri':304C 'id':103C 'identifi':142C 'immedi':247C 'impact':192C 'import':111C 'includ':49B,253C 'incorpor':242C 'inform':7A,78C,93C 'insert':4A,75C,90C 'insid':41B 'issu':147C,212C,311C 'jvgp':19A,24A,296C 'lab':28B 'lab-disclosur':27B 'latest':233C 'learn':136C 'librari':130C 'like':301C 'log':9A,57B,66B,80C,95C,173C,184C,264C,271C,287C 'machin':135C 'ml':31B 'ml-pipelin':30B 'model':137C 'obtain':188C 'open':128C 'oper':161C,276C 'output':48B,168C,269C,288C 'packag':33B 'pdt':120C 'pipelin':32B 'plaintext':70B,190C 'pleas':318C 'possibl':251C 'present':283C 'process':317C 'public':114C 'python':14A,34B,44B,85C,100C,124C,155C,196C,204C,219C,267C 'question':324C 'read':64B 'recommend':229C 'recov':68B 'redact':59B,175C 'refer':289C 'remot':178C 'repositori':50B,163C,257C 'requir':112C 'resolut':210C 'restrict':260C 'review':270C 'rotat':278C 'sagemak':13A,35B,43B,84C,99C,123C,140C,154C,195C,203C,218C,266C 'sankar':305C 'scope':107C 'sdk':15A,45B,86C,101C,125C,156C,197C,205C,220C,268C 'secur':323C 'sensit':6A,77C,92C 'sourc':129C 'subprocess':166C 'thank':303C 'train':132C 'type':110C 'upgrad':230C,248C 'url':258C 'user':179C 'v2':198C,221C 'v3':206C,225C 'version':193C,199C,207C,222C,226C,234C 'vulner':315C 'without':58B,174C 'workaround':245C 'would':300C 'written':54B,170C","nicknames":[],"mitigations":[],"who_affected":"Teams that run the SageMaker Python SDK to clone Git repositories during training or deployment and whose clone URLs carry credentials. Exposure also depends on who can read the CloudWatch log groups where that output lands. Teams on a patched version, or not using credentials in Git URLs, can skip it.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-14T00:00:00+00:00","kev":null,"cvss_vector":null,"cvss_by":null,"poc_count":0,"sources":[{"source":"lab","external_id":"https://aws.amazon.com/security/security-bulletins/rss/2026-134-aws/#GHSA-g6w4-jvgp-68x2","url":"https://aws.amazon.com/security/security-bulletins/rss/2026-134-aws/","severity":null,"published_at":"2026-10-14T00:00:00+00:00","modified_at":null,"first_seen_at":"2026-10-24T20:05:36+00:00","fetched_at":"2026-10-24T20:05:36+00:00","note":"AWS: CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK"}],"documents":[{"id":2976,"url":"https://aws.amazon.com/security/security-bulletins/rss/2026-134-aws/","title":"AWS: CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK","kind":"advisory","source":"lab","text":"CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK\n\n### CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK\n\nBulletin ID: 2026-134-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/14/2026 11:30 AM PDT\n\nDescription:\n\nAmazon SageMaker Python SDK is an open source library for training and deploying machine learning models on Amazon SageMaker.\n\nWe 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.\n\nImpacted versions:\n\n- Amazon SageMaker Python SDK V2 versions before 2.257.3\n- Amazon SageMaker Python SDK V3 versions before 3.10.0\n\nResolution:\n\nThis 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.\n\nWorkarounds:\n\nIf 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.\n\nReferences:\n\n- CVE-2026-110248\n- GHSA-g6w4-jvgp-68x2\n\nAcknowledgement:\n\nWe would like to thank Gouri Sankar A for collaborating on this issue through the coordinated vulnerability disclosure process.\n\n Please email aws-security@amazon.com with any security questions or concerns.","published_at":"2026-10-14T00:00:00+00:00","relation":"advisory","confidence":null,"note":null}],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}