Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-1777: CWE-319 Cleartext Transmission of Sensitive Information in AWS SageMaker Python SDK

0
High
VulnerabilityCVE-2026-1777cvecve-2026-1777cwe-319
Published: Mon Feb 02 2026 (02/02/2026, 20:10:03 UTC)
Source: CVE Database V5
Vendor/Project: AWS
Product: SageMaker Python SDK

Description

The Amazon SageMaker Python SDK before v3.2.0 and v2.256.0 includes the ModelBuilder HMAC signing key in the cleartext response elements of the DescribeTrainingJob function. A third party with permissions to both call this API and permissions to modify objects in the Training Jobs S3 output location may have the ability to upload arbitrary artifacts which are executed the next time the Training Job is invoked.

AI-Powered Analysis

AILast updated: 02/02/2026, 23:34:06 UTC

Technical Analysis

CVE-2026-1777 is a vulnerability identified in the AWS SageMaker Python SDK versions before 3.2.0 and 2.256.0. The issue arises because the DescribeTrainingJob API call returns the ModelBuilder HMAC signing key in cleartext within its response elements. This key is intended to secure the integrity and authenticity of model-building operations. However, its exposure allows an attacker who has permissions to both call the DescribeTrainingJob API and modify objects in the S3 bucket used for Training Job outputs to upload arbitrary artifacts. These malicious artifacts can be executed the next time the training job runs, effectively enabling remote code execution within the SageMaker training environment. The vulnerability is classified under CWE-319, which concerns the cleartext transmission of sensitive information. The CVSS v3.1 base score is 7.2, reflecting high severity due to network attack vector, low attack complexity, required privileges, and high impact on confidentiality, integrity, and availability. The exploit does not require user interaction but does require the attacker to have elevated permissions, which may be obtained through misconfiguration or insider threat. No public patches are linked yet, and no known exploits have been reported in the wild. The vulnerability highlights the risk of sensitive key exposure in cloud SDKs and the critical need for strict access controls and secure handling of cryptographic keys in AI/ML pipelines.

Potential Impact

For European organizations leveraging AWS SageMaker for machine learning workloads, this vulnerability poses a significant risk. Exposure of the ModelBuilder HMAC key can lead to unauthorized modification of training artifacts, resulting in execution of arbitrary code within the training environment. This can compromise the confidentiality of sensitive training data and models, integrity of AI workflows, and availability of AI services. Attackers could implant backdoors or malicious code into models, potentially undermining AI decision-making processes or causing denial of service. Given the increasing reliance on AI/ML in sectors such as finance, healthcare, and manufacturing across Europe, the impact could extend to critical infrastructure and sensitive personal data processing. The requirement for elevated permissions reduces the attack surface but also indicates that insider threats or compromised credentials could be exploited. The lack of known exploits suggests limited immediate risk but does not diminish the urgency for remediation due to the high potential impact.

Mitigation Recommendations

European organizations should immediately upgrade the AWS SageMaker Python SDK to versions 3.2.0 or later (or 2.256.0 or later) where this vulnerability is addressed. Until patches are applied, organizations must enforce strict IAM policies to limit who can call the DescribeTrainingJob API and who can modify objects in the S3 output buckets associated with training jobs. Implement fine-grained access controls and monitor for unusual API calls or S3 object modifications. Employ logging and alerting on these activities to detect potential exploitation attempts. Additionally, consider isolating training jobs and their output storage to minimize the blast radius of any compromise. Regularly audit permissions and rotate any exposed keys or credentials. Finally, integrate security reviews into AI/ML pipeline development to ensure cryptographic keys and sensitive information are never exposed in cleartext responses or logs.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
AMZN
Date Reserved
2026-02-02T18:13:49.829Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69813004f9fa50a62f63a397

Added to database: 2/2/2026, 11:15:16 PM

Last enriched: 2/2/2026, 11:34:06 PM

Last updated: 2/7/2026, 7:54:27 PM

Views: 35

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats