{"id":"GHSA-w64x-664p-7w66","kind":"vulnerability","aliases":["GHSA-w64x-664p-7w66"],"related":[],"title":"CVE-2026-104019 - OS command injection in the Studio Space startup script in Amazon SageMaker Distribution","description":"CVE-2026-104019 - OS command injection in the Studio Space startup script in Amazon SageMaker Distribution\n\n### CVE-2026-104019 - OS command injection in the Studio Space startup script in Amazon SageMaker Distribution\n\nBulletin ID: 2026-125-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/02/2026 13:00 PM PDT\n\nDescription:\n\nAmazon 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.\n\nWe 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.\n\nWe 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.\n\nImpacted versions:\n\n- 2.8.x - 2.13.x: all versions affected, no fix (end of support)\n- 2.14.x: < 2.14.12, fixed in 2.14.12\n- 3.3.x - 3.8.x: all versions affected, no fix (end of support)\n- 3.9.x: < 3.9.12, fixed in 3.9.12\n- 4.0.x: < 4.0.11, fixed in 4.0.11\n- 4.1.x: < 4.1.11, fixed in 4.1.11\n- 4.2.x: < 4.2.8, fixed in 4.2.8\n- 4.3.x: < 4.3.5, fixed in 4.3.5\n- 4.4.x: < 4.4.3, fixed in 4.4.3\n- 4.5.x: not affected\n- < 2.8.0 and < 3.3.0: not affected\n\nResolution:\n\nThis 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.\n\nWorkarounds:\n\nNone.\n\nReferences:\n\n- CVE-2026-104019\n- GHSA-w64x-664p-7w66\n\n Please email aws-security@amazon.com with any security questions or concerns.","summary":"The 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.","severity":"high","cvss":null,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["aws","infrastructure","lab-disclosure","sagemaker","sagemaker-unified-studio","trusted-identity-propagation"],"not_affected_if":["single-member-project","version-4.5.x","version-below-2.8.0-or-3.3.0"],"how_to_check":"- Check the SageMaker Distribution image version of each Studio Space against the impacted ranges in the bulletin, for example by reviewing the image tag or the Space's image in SageMaker Unified Studio.\n- Check whether the project has Trusted Identity Propagation enabled.\n- Check the SageMaker Distribution version line: 2.8.x through 2.13.x and 3.3.x through 3.8.x have no fix.","fix":"- Restart Studio Spaces so they pick up the latest patch of their minor line: `2.14.12`, `3.9.12`, `4.0.11`, `4.1.11`, `4.2.8`, `4.3.5`, or `4.4.3`.\n- Move Spaces on unsupported lines (2.8.x to 2.13.x, 3.3.x to 3.8.x) to a supported version, since no fix is provided for them.\n- Workarounds: none.","status":"open","published_at":null,"first_seen_at":"2026-10-24T19:12:57+00:00","triaged_at":"2026-10-25T04:51:38+00:00","updated_at":"2026-10-25T04:51:38+00:00","category":"infrastructure","confidence":0.6,"triage":{"at":"2026-10-25T04:51:38Z","model":"claude-haiku-5-5","output":{"fix":"- Restart Studio Spaces so they pick up the latest patch of their minor line: `2.14.12`, `3.9.12`, `4.0.11`, `4.1.11`, `4.2.8`, `4.3.5`, or `4.4.3`.\n- Move Spaces on unsupported lines (2.8.x to 2.13.x, 3.3.x to 3.8.x) to a supported version, since no fix is provided for them.\n- Workarounds: none.","reach":"internet","title":"Amazon SageMaker Distribution: command injection in Studio Space startup script","impact":"high","summary":"The 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.","category":"infrastructure","nicknames":[],"who_cares":["aws","sagemaker","sagemaker-unified-studio","trusted-identity-propagation"],"confidence":0.6,"needs_auth":"yes","worst_case":"Another member's code runs in their Space and temporary role credentials can be stolen.","analyst_note":"Check the AWS bulletin 2026-125-AWS and the GHSA entry for the exact trigger conditions and whether single-member projects are exposed.","how_to_check":"- Check the SageMaker Distribution image version of each Studio Space against the impacted ranges in the bulletin, for example by reviewing the image tag or the Space's image in SageMaker Unified Studio.\n- Check whether the project has Trusted Identity Propagation enabled.\n- Check the SageMaker Distribution version line: 2.8.x through 2.13.x and 3.3.x through 3.8.x have no fix.","needs_analyst":true,"not_affected_if":["version-4.5.x","version-below-2.8.0-or-3.3.0","single-member-project"],"who_is_affected":"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.","user_interaction":"no","needs_special_setup":"yes","severity_if_unknown":"high"},"cost_usd":0.000849,"input_tokens":4288,"output_tokens":840,"severity_before":"unknown"},"analyst_status":null,"analyst_note":null,"search":"'-104019':3A,100C,116C,189C,469C '-125':133C '-2026':2A,99C,115C,188C,468C '00':146C '10/02/2026':144C '13':145C '2.13':331C '2.14':341C '2.14.12':343C,346C,414C '2.8':329C '2.8.0':399C '2026':132C '3.3':347C '3.3.0':401C '3.8':349C '3.9':359C '3.9.12':361C,364C,415C '4.0':365C '4.0.11':367C,370C,416C '4.1':371C '4.1.11':373C,376C,417C '4.2':377C '4.2.8':379C,382C,418C '4.3':383C '4.3.5':385C,388C,419C '4.4':389C '4.4.3':391C,394C,421C '4.5':395C '664p':20A,25A,473C '7w66':21A,26A,474C 'access':170C,270C 'act':176C 'address':409C 'adopt':429C 'affect':335C,353C,398C,403C 'ai':163C 'allow':234C 'also':84B 'amazon':14A,111C,127C,150C,423C 'analyt':161C 'anoth':69B,86B,244C,272C 'appli':318C 'arbitrari':64B,235C 'attent':141C 'automat':322C 'avail':216C 'aw':27B,96B,134C,136C,156C,287C 'aws-security@amazon.com':477C 'behalf':291C 'built':183C 'bulletin':130C 'call':94B,280C 'certain':62B,223C 'code':65B,236C 'command':5A,102C,118C 'concern':483C 'condit':63B,224C 'connect':54B,218C,228C,304C 'content':137C 'contributor':82B,265C 'could':83B,233C,258C 'credenti':92B,278C 'cve':1A,98C,114C,187C,467C 'data':160C,174C 'date':143C 'deploy':314C,444C 'descript':149C 'detail':55B,229C,305C 'develop':164C 'disclosur':31B 'distribut':16A,113C,129C,300C,412C 'downstream':95B,281C 'email':476C 'enabl':80B,255C,286C 'end':338C,356C 'execut':90B,239C,276C 'featur':254C 'find':168C 'fix':295C,312C,337C,344C,355C,362C,368C,374C,380C,386C,392C 'gain':269C 'ghsa':18A,23A,471C 'ghsa-w64x-664p-7w66':17A,22A,470C 'global':315C 'higher':268C 'id':131C 'ident':39B,78B,252C,283C 'identifi':186C 'imag':442C 'impact':327C 'implement':293C 'import':139C 'improp':225C 'infrastructur':28B 'inject':6A,103C,119C 'integr':180C 'issu':191C,257C,406C 'lab':30B 'lab-disclosur':29B 'latest':431C 'let':166C 'line':436C 'member':71B,87B,246C,273C 'minor':435C,458C 'network':58B,211C 'next':325C 'none':465C 'obtain':85B 'organ':172C 'os':4A,101C,117C 'patch':432C,441C 'pdt':148C 'perform':209C 'permiss':266C 'pleas':475C 'pm':147C 'process':310C 'project':70B,75B,221C,245C,248C,264C 'propag':40B,79B,253C,285C 'propagation-en':284C 'public':142C 'purpos':182C 'purpose-built':181C 'question':481C 'receiv':461C 'recommend':452C 'refer':466C 'requir':140C,450C 'resolut':404C 'restart':438C,453C 'result':259C 'role':91B,277C 'run':67B 'sagemak':15A,32B,34B,45B,48B,112C,128C,151C,196C,199C,207C,217C,299C,411C,424C 'sagemaker-unified-studio':33B 'sanit':53B,226C,303C 'scope':135C 'script':12A,43B,109C,125C,204C 'secur':480C 'select':448C 'servic':97B,157C,288C 'space':10A,46B,73B,107C,123C,197C,208C,242C,321C,428C,455C 'startup':11A,42B,108C,124C,194C,203C,308C,326C 'studio':9A,36B,50B,106C,122C,153C,201C,426C,427C 'support':298C,340C,358C 'temporari':89B,275C 'tool':184C 'trust':38B,77B,251C,282C 'trusted-identity-propag':37B 'type':138C 'unifi':35B,49B,152C,159C,200C,425C 'updat':463C 'user':262C 'valid':59B,212C,232C,309C 'version':301C,328C,334C,352C,413C,447C,459C 'w64x':19A,24A,472C 'workaround':464C 'x':330C,332C,342C,348C,350C,360C,366C,372C,378C,384C,390C,396C","nicknames":[],"mitigations":[],"who_affected":"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.","tier":"B","verified":{},"analyst_revisit_at":null,"first_public_at":null,"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-125-aws/#GHSA-w64x-664p-7w66","url":"https://aws.amazon.com/security/security-bulletins/rss/2026-125-aws/","severity":null,"published_at":null,"modified_at":null,"first_seen_at":"2026-10-24T19:12:57+00:00","fetched_at":"2026-10-24T19:12:57+00:00","note":"AWS: CVE-2026-104019 - OS command injection in the Studio Space startup script in Amazon SageMaker Distribution"}],"documents":[{"id":2930,"url":"https://aws.amazon.com/security/security-bulletins/rss/2026-125-aws/","title":"AWS: CVE-2026-104019 - OS command injection in the Studio Space startup script in Amazon SageMaker Distribution","kind":"advisory","source":"lab","text":"CVE-2026-104019 - OS command injection in the Studio Space startup script in Amazon SageMaker Distribution\n\n### CVE-2026-104019 - OS command injection in the Studio Space startup script in Amazon SageMaker Distribution\n\nBulletin ID: 2026-125-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/02/2026 13:00 PM PDT\n\nDescription:\n\nAmazon 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.\n\nWe 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.\n\nWe 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.\n\nImpacted versions:\n\n- 2.8.x - 2.13.x: all versions affected, no fix (end of support)\n- 2.14.x: < 2.14.12, fixed in 2.14.12\n- 3.3.x - 3.8.x: all versions affected, no fix (end of support)\n- 3.9.x: < 3.9.12, fixed in 3.9.12\n- 4.0.x: < 4.0.11, fixed in 4.0.11\n- 4.1.x: < 4.1.11, fixed in 4.1.11\n- 4.2.x: < 4.2.8, fixed in 4.2.8\n- 4.3.x: < 4.3.5, fixed in 4.3.5\n- 4.4.x: < 4.4.3, fixed in 4.4.3\n- 4.5.x: not affected\n- < 2.8.0 and < 3.3.0: not affected\n\nResolution:\n\nThis 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.\n\nWorkarounds:\n\nNone.\n\nReferences:\n\n- CVE-2026-104019\n- GHSA-w64x-664p-7w66\n\n Please email aws-security@amazon.com with any security questions or concerns.","published_at":null,"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"}