Live › vulnerability › GHSA-w64x-664p-7w66
Go to dashboardThe startup script for SageMaker Spaces in SageMaker Unified Studio does not sanitize connection details during its network validation, so under certain conditions arbitrary code can run in another project member's Space. In projects with Trusted Identity Propagation enabled, a contributor could also obtain another member's temporary execution role credentials and call downstream AWS services as them.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-24 19:12 UTC. All times on this page are UTC.
Teams using SageMaker Unified Studio Spaces on affected SageMaker Distribution versions are exposed, particularly projects with several members and Trusted Identity Propagation enabled. Versions 4.5.x and anything below 2.8.0 or 3.3.0 are not affected according to the bulletin.
No product ranges from the sources yet.
2.14.12, 3.9.12, 4.0.11, 4.1.11, 4.2.8, 4.3.5, or 4.4.3.Each 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("GHSA-w64x-664p-7w66")