CVE-2026-104019 can cross between SageMaker Studio Spaces
AWS says unsanitized SageMaker connection details in Space startup validation could execute commands in another project member's Space. Check the Distribution branch and restart affected Spaces so the deployed fix takes effect.
Imagine several people have separate workbenches in one workshop. When a bench starts, it checks the project's shared connection list. A command-shaped value in that list could make the startup check run in another person's workspace. The fix sanitizes connection details; administrators still need the Space to restart onto the corrected image.
| SageMaker Distribution line | CVE-2026-104019 status | Action |
|---|---|---|
| 2.8.x–2.13.x | Affected; end of support | No patch for these lines. Migrate to a supported line. |
| 2.14.x before 2.14.12 | Affected | Restart the Space; Unified Studio automatically applies the latest patch in this minor line (fixed from 2.14.12). |
| 3.3.x–3.8.x | Affected; end of support | No patch for these lines. Migrate to a supported line. |
| 3.9.x before 3.9.12 | Affected | Restart the Space; Unified Studio automatically applies the latest patch in this minor line (fixed from 3.9.12). |
| 4.0.x before 4.0.11 | Affected | Restart the Space; Unified Studio automatically applies the latest patch in this minor line (fixed from 4.0.11). |
| 4.1.x before 4.1.11 | Affected | Restart the Space; Unified Studio automatically applies the latest patch in this minor line (fixed from 4.1.11). |
| 4.2.x before 4.2.8 | Affected | Restart the Space; Unified Studio automatically applies the latest patch in this minor line (fixed from 4.2.8). |
| 4.3.x before 4.3.5 | Affected | Restart the Space; Unified Studio automatically applies the latest patch in this minor line (fixed from 4.3.5). |
| 4.4.x before 4.4.3 | Affected | Restart the Space; Unified Studio automatically applies the latest patch in this minor line (fixed from 4.4.3). |
| 4.5.x | Not affected | No action for this CVE. |
| 2.x before 2.8.0 or 3.x before 3.3.0 | Not affected | No action for this CVE. |
CVE-2026-104019 affected versions and impact
During Space startup, a validation script checks the project's available SageMaker connections. AWS says improper sanitization of connection details could allow a project contributor or higher to execute commands in another member's Space. The impact is conditional: where Trusted Identity Propagation is enabled, AWS says the issue could also expose the other member's temporary execution-role credentials for use with downstream services that honor that identity. AWS does not publish the affected script, the exact connection property, or a code-level patch diff. Do not infer that every contributor can read all project data or that every deployment enables Trusted Identity Propagation.
How to fix CVE-2026-104019 in SageMaker
- Inventory SageMaker Unified Studio projects and Spaces, recording each Space's Distribution minor line and whether Trusted Identity Propagation is enabled.
- For affected supported lines, restart each Space so it adopts the globally deployed fixed image. AWS says Spaces use the latest patch of their minor line after restart; administrators do not select a separate patch version in Unified Studio.
- Move Spaces on 2.8.x–2.13.x or 3.3.x–3.8.x to a supported line. AWS lists those branches as end-of-support and says no fix is available for them.
- Verify after restart that the Space runs the patched minor-line build listed above. Recheck any Space that remained running during the rollout.
- Review project membership and downstream Trusted Identity Propagation activity if there is a reason to suspect misuse. AWS's advisory does not report confirmed exploitation; follow your incident process and credential response policy if investigation finds evidence.
- Do not rely on a workaround: AWS lists none. The listed remediation is the fixed Distribution image, applied on the next Space startup.