Live › vulnerability › CVE-2026-104019
Go to dashboardA flaw in the startup validation script of SageMaker Spaces lets improper sanitization of connection details run arbitrary OS commands inside a Space. In projects with Trusted Identity Propagation, another project member can reach the victim's temporary execution role credentials.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-24 19:12 UTC, 0h before NVD. All times on this page are UTC.
Teams running SageMaker Spaces in Amazon SageMaker Unified Studio on an affected SageMaker Distribution image, most of all projects with Trusted Identity Propagation enabled, where a contributor can reach another member's execution role credentials. The fix is deployed globally and applies on the next Space restart, but Spaces on end-of-support lines get no fix at all.
No product ranges from the sources yet.
2.14.x below 2.14.12, 3.9.x below 3.9.12, 4.0.x below 4.0.11, 4.1.x below 4.1.11, 4.2.x below 4.2.8, 4.3.x below 4.3.5, 4.4.x below 4.4.3 are affected2.8.x through 2.13.x and 3.3.x through 3.8.x are affected with no fix (end of support)4.5.x and anything below 2.8.0 or 3.3.0 are not affected2.14.12, 3.9.12, 4.0.11, 4.1.11, 4.2.8, 4.3.5, 4.4.32.8.x to 2.13.x, 3.3.x to 3.8.x) to a supported version; no patch is providedEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
CVE-2026-104019 - OS command injection in the Studio Space startup script in Amazon SageMaker Distribution
Bulletin ID: 2026-125-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/02/2026 13:00 PM PDT
Description:
Amazon SageMaker Unified Studio is an AWS service that unifies data, analytics, and AI development. It lets you find and access your organization's data and act on it with integrated, purpose-built tools.
We identified CVE-2026-104019, an issue with the startup of SageMaker Spaces in SageMaker Unified Studio. The startup script in a SageMaker Space performs a network validation against all the available SageMaker connections in a project. Under certain conditions, improper sanitization of connection details during this validation could allow arbitrary code to be executed in the Space of another project member. In projects with the Trusted Identity Propagation feature enabled, this issue could result in a user with project contributor permissions (or higher) gaining access to another member's temporary execution role credentials and calling downstream trusted identity propagation-enabled AWS services on their behalf.
We implemented a fix to all supported SageMaker Distribution versions to sanitize connection details during the startup validation process. The fix is deployed globally and will apply to all Spaces automatically on the next startup.
Impacted versions:
Resolution:
This issue has been addressed in SageMaker Distribution versions 2.14.12, 3.9.12, 4.0.11, 4.1.11, 4.2.8, 4.3.5, and 4.4.3. In Amazon SageMaker Unified Studio, Studio Spaces adopt the latest patch of their minor line on restart once the patched images are deployed, so no version selection is required. We recommend restarting any spaces for these minor versions to receive this update.
Workarounds:
None.
References:
Please email [email protected] with any security questions or concerns.
This page as .md · .json · in your agent: get_signal("CVE-2026-104019")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.