AWS Security Bulletins: CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK
AWS Security Bulletins has published a new security advisory. Here is a summary and what to do.
Key points
- New advisory from AWS Security Bulletins.
- Review affected versions in the advisory.
- Apply updates promptly.
AWS Security Bulletins published a security advisory titled “CVE-2026-110248 - Insertion of sensitive information into log files in Amazon SageMaker Python SDK”.
At a glance
- Publisher
- AWS Security Bulletins
- CVEs
- CVE-2026-110248
What the advisory says
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 Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.
What should you do?
- Read the full vendor advisory linked below and confirm whether you run affected versions.
- Schedule the recommended update, prioritising internet-facing systems.
- Watch for exploitation reports; unpatched edge devices are frequent targets.
What to do and how to stay safe: CVE-2026-110248
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
