--- id: "CVE-2026-104019" kind: "vulnerability" aliases: ["CVE-2026-104019"] title: "Amazon SageMaker Distribution: command injection in Space startup script" severity: "critical" cvss: 9.3 epss: 0.01419 exploited: false status: "open" category: "infrastructure" products: [] ecosystems: [] tags: ["aws", "data-science", "infrastructure", "lab-disclosure", "sagemaker", "sagemaker-unified-studio"] not_affected_if: ["pre-2.8-or-pre-3.3", "version-4.5"] published_at: "2026-10-02T20:17:00+00:00" first_seen_at: "2026-10-24T19:12:57+00:00" updated_at: "2026-10-25T12:38:49+00:00" sources: [{"source": "lab", "url": "https://aws.amazon.com/security/security-bulletins/rss/2026-125-aws/", "first_seen_at": "2026-10-24T19:12:57+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-104019", "first_seen_at": "2026-10-24T19:23:38+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-104019", "first_seen_at": "2026-10-25T12:38:49+00:00"}] --- # Amazon SageMaker Distribution: command injection in Space startup script A 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, check and fix written by a model from the sources; labelled as such._ ## How to check - Check the SageMaker Distribution image version in use: `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 affected - Versions `2.8.x` through `2.13.x` and `3.3.x` through `3.8.x` are affected with no fix (end of support) - Versions `4.5.x` and anything below `2.8.0` or `3.3.0` are not affected ## Fix - Restart all SageMaker Spaces on the affected minor lines so they pick up the patched image: `2.14.12`, `3.9.12`, `4.0.11`, `4.1.11`, `4.2.8`, `4.3.5`, `4.4.3` - Move Spaces on end-of-support lines (`2.8.x` to `2.13.x`, `3.3.x` to `3.8.x`) to a supported version; no patch is provided - No workaround is documented by AWS ## Timeline - 2026-10-24T19:12:57+00:00 lab https://aws.amazon.com/security/security-bulletins/rss/2026-125-aws/ — AWS: CVE-2026-104019 - OS command injection in the Studio Space startup script in Amazon SageMaker Distribution - 2026-10-24T19:23:38+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-104019 - 2026-10-25T12:38:49+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-104019 ## Documents - [advisory] AWS: CVE-2026-104019 - OS command injection in the Studio Space startup script in Amazon SageMaker Distribution https://aws.amazon.com/security/security-bulletins/rss/2026-125-aws/ ## From the sources CVE-2026-104019 - OS command injection in the Studio Space startup script in Amazon SageMaker Distribution ### 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: - 2.8.x - 2.13.x: all versions affected, no fix (end of support) - 2.14.x: < 2.14.12, fixed in 2.14.12 - 3.3.x - 3.8.x: all versions affected, no fix (end of support) - 3.9.x: < 3.9.12, fixed in 3.9.12 - 4.0.x: < 4.0.11, fixed in 4.0.11 - 4.1.x: < 4.1.11, fixed in 4.1.11 - 4.2.x: < 4.2.8, fixed in 4.2.8 - 4.3.x: < 4.3.5, fixed in 4.3.5 - 4.4.x: < 4.4.3, fixed in 4.4.3 - 4.5.x: not affected - < 2.8.0 and < 3.3.0: not affected 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: - CVE-2026-104019 - GHSA-w64x-664p-7w66 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_