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

Machine-generated threat intelligence

AILast updated: 02/10/2026, 10:49:14 UTC

Technical Analysis

CVE-2026-1777 is a vulnerability classified under CWE-319 (Cleartext Transmission of Sensitive Information) affecting the AWS SageMaker Python SDK versions prior to 3.2.0 and 2.256.0. The issue arises because the ModelBuilder HMAC signing key is included in the cleartext response elements of the DescribeTrainingJob API call. This key is critical for authenticating and validating artifacts used in training jobs. If an attacker has both the ability to invoke the DescribeTrainingJob API and permissions to modify objects in the S3 bucket where training job outputs are stored, they can upload arbitrary artifacts. These malicious artifacts can then be executed during the next training job run, effectively allowing code execution within the SageMaker training environment. This chain of exploitation requires a high privilege level (permissions to call the API and modify S3 objects) but no user interaction. The vulnerability has a CVSS v3.1 score of 7.2, indicating high severity due to its impact on confidentiality, integrity, and availability. Although no known exploits are currently reported in the wild, the potential for significant damage exists, especially in environments relying heavily on automated machine learning pipelines. The vulnerability underscores the risk of sensitive key exposure in API responses and the importance of strict access controls on cloud resources.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of machine learning models and data processed within AWS SageMaker environments. Compromise could lead to unauthorized code execution, data leakage, or manipulation of training outputs, potentially affecting critical business operations and intellectual property. Given the increasing adoption of AI/ML services across sectors such as finance, healthcare, and manufacturing in Europe, exploitation could disrupt services, cause regulatory compliance issues (e.g., GDPR violations due to data exposure), and damage organizational reputation. The requirement for elevated permissions limits exposure to insiders or attackers who have already breached initial defenses, but the impact remains severe if exploited. Additionally, the ability to execute arbitrary code in training jobs could be leveraged to pivot within cloud environments, escalating the threat beyond the initial compromise.

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) to eliminate the vulnerability. Access controls must be tightened to enforce the principle of least privilege, ensuring that only trusted users and services have permissions to call the DescribeTrainingJob API and modify S3 training job output buckets. Implement monitoring and alerting on unusual API calls and S3 object modifications related to SageMaker training jobs. Employ AWS IAM policies with explicit deny rules for unnecessary permissions and consider using AWS CloudTrail and AWS Config to audit and detect suspicious activities. Additionally, segregate training job output buckets per project or team to limit blast radius. Where possible, implement encryption and integrity checks on artifacts stored in S3 to detect unauthorized modifications. Finally, conduct regular security reviews of cloud resource permissions and update incident response plans to include scenarios involving cloud-based ML pipeline compromises.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

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/10/2026, 10:49:14 AM

Last updated: 3/24/2026, 10:55:19 AM

Views: 74

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses