sagemaker-distribution: Improper Neutralization of Special Elements used in an OS Command
CVE-2026-104019 is a critical-severity improper neutralization of special elements used in an OS command vulnerability in sagemaker-distribution from AWS, with a CVSS 3.1 base score of 9.0 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. The record lists versions 2.14.12, 3.9.12, 4.0.11 as the first without the flaw, so updating sagemaker-distribution to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.45% chance of exploitation within 30 days, higher than 74% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update sagemaker-distribution to 2.14.12 or 3.9.12 or 4.0.11 or 4.1.11, whichever matches your release line, or a later version.
- Read the advisory on aws.amazon.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| AWS | sagemaker-distribution | 2.8.0 up to, but not including, 2.14.12; 3.3.0 up to, but not including, 3.9.12; 4.0.0 up to, but not including, 4.0.11; 4.1.0 up to, but not including, 4.1.11; 4.2.0 up to, but not including, 4.2.8; 4.3.0 up to, but not including, 4.3.5; 4.4.0 up to, but not including, 4.4.3 | 2.14.12, 3.9.12, 4.0.11, 4.1.11, 4.2.8, 4.3.5 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 9.3 | Critical | CNA |
| CVSS 3.1 | 9.0 | Critical | CNA |
Official description
OS command injection in the Studio Space startup validation script in Amazon SageMaker Distribution 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, as used by Amazon SageMaker Unified Studio, might allow an authenticated remote user with project contributor permissions to 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 that is interpolated into a shell invocation without neutralization. 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 use. Users on minor lines that have reached end of support must move to a supported minor line, because no patched version will be released for those lines. 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in an OS Command
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command before it is sent to a downstream component.
How developers prevent this class of flaw
- If at all possible, use library calls rather than external processes to recreate the desired functionality.
- For any data that will be used to generate a command to be executed, keep as much of that data out of external control as possible. For example, in web applications, this may require storing the data locally in the session's state instead of sending it out to the client in a hidden form field.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
More Improper Neutralization of Special Elements used in an OS Command vulnerabilities (CWE-78)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other references
Recent Improper Neutralization of Special Elements used in an OS Command vulnerabilities
- 9.4 Critical severity
- 7.3 High severity
- 7.7 High severity
- 7.8 High severity
- 8.5 High severity
- 8.2 High severity
Spotted an error? Tell us.