CVE-2026-104019 AWS CVE debrief

Who should care

Defenders responsible for Amazon SageMaker Distribution and Unified Studio deployments should assess exposure and prioritize remediation. Specifically, those with project contributor permissions or managing Studio Spaces should verify their versions and upgrade as necessary.

Why it matters

This critical vulnerability in Amazon SageMaker Distribution requires immediate attention from defenders. An authenticated remote user with project contributor permissions could exploit this issue to execute arbitrary commands in another project member's Studio Space and obtain their temporary execution role credentials. Defenders should assess exposure, prioritize remediation, and verify that Studio Spaces adopt the latest patch of their minor line on restart.

• Potential lateral movement within Studio Spaces
• Elevation of privileges for authenticated remote users
• Exposure of temporary execution role credentials
• Possible disruption of Studio Space operations

Technical summary

The vulnerability exists in the Studio Space startup validation script in Amazon SageMaker Distribution. An authenticated remote user with project contributor permissions could execute arbitrary commands in another project member's Studio Space and obtain that member's temporary execution role credentials via a crafted connection resource property. This issue affects multiple versions of SageMaker Distribution, including 2.x before 2.14.12, 3.x before 3.9.12, 4.0.x before 4.0.11, 4.1.x before 4.1.11, 4.2.x before 4.2.8, 4.3.x before 4.3.5, and 4.4.x before 4.4.3. To remediate this issue, users should upgrade to version 2.14.12, 3.9.12, 4.0.11, 4.1.11, 4.2.8, 4.3.5, or 4.4.3, as applicable to the minor line in

Defensive priority

High

Recommended defensive actions

• Upgrade to version 2.14.12, 3.9.12, 4.0.11, 4.1.11, 4.2.8, 4.3.5, or 4.4.3, as applicable to the minor line in use.
• Users on minor lines that have reached end of support must move to a supported minor line.
• Verify that Studio Spaces adopt the latest patch of their minor line on restart once the patched images are deployed.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and remediation steps. However, the corpus does not establish evidence of exploitation or specific business impacts.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.