dbcve.org
Cleartext TransmissionWeakness · CWE-319

CVE-2026-1777

HIGH · 7.2 CVSS v3.1 Published 2026-02-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Amazon SageMaker Python SDK before v3.2.0 and v2.256.0 exposes the ModelBuilder HMAC signing key in plaintext within DescribeTrainingJob API responses. An attacker with both API call permissions and S3 write access to training output locations can inject malicious artifacts that execute on subsequent training job runs.

MitigationUpgrade SageMaker Python SDK to v3.2.0 or v2.256.0 or later to remediate the key exposure. Additionally, rotate any potentially exposed HMAC signing keys and audit access controls to ensure least-privilege permissions on DescribeTrainingJob and S3 bucket access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed SageMaker Python SDK version
    Run 'pip show amazon-sagemaker' or execute 'python -c "import sagemaker; print(sagemaker.__version__)"' to retrieve the SDK version
    Affected if Version is below 2.256.0 for the v2.x branch or below 3.2.0 for the v3.x branch
  2. Confirm use of ModelBuilder with HMAC signing
    Review training job creation code for imports of 'sagemaker.workflow.model_builder' and usage of 'signing_config' or 'hmac_key' parameters when constructing models
    Affected if Code uses ModelBuilder with HMAC signing configuration enabled for model packages
  3. Audit DescribeTrainingJob API access
    Review IAM policies attached to roles/users that have access to SageMaker, specifically check for 'sagemaker:DescribeTrainingJob' permission in permission policies
    Affected if Any role or user beyond the training job creator has sagemaker:DescribeTrainingJob permission
  4. Review S3 bucket permissions for training outputs
    Examine S3 bucket policies and IAM policies granting access to the bucket configured as 'output_path' or 's3_output_location' for training jobs; check for write permissions to principals other than the training job execution role
    Affected if Principals other than the training job execution role have s3:PutObject or s3:PutObjectAcl permissions to training output buckets

Your environment is affected if the SageMaker Python SDK version is below v2.256.0 or v3.2.0 AND you use ModelBuilder with HMAC signing AND both DescribeTrainingJob API access and S3 write access to training outputs are accessible to the same principal (including potential attackers).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SageMaker Python SDK to v3.2.0 or v2.256.0 or later to remediate the key exposure. Additionally, rotate any potentially exposed HMAC signing keys and audit access controls to ensure least-privilege permissions on DescribeTrainingJob and S3 bucket access.

Recommended fix Moderate confidence

Amazon SageMaker Python SDK v3.2.0 (for v3.x) or v2.256.0 (for v2.x)

  1. Check the current installed version of Amazon SageMaker Python SDK using pip show amazon-sagemaker-python-sdk or pip list | grep sagemaker
  2. Upgrade to version v3.2.0 or later if using the v3.x line: pip install amazon-sagemaker-python-sdk>=3.2.0
  3. Alternatively, upgrade to version v2.256.0 or later if using the v2.x line: pip install amazon-sagemaker-python-sdk>=2.256.0
  4. Verify the upgrade was successful by checking the installed version again
  5. Review any release notes for the target version to ensure compatibility with your existing code
Caveat Review SDK release notes as minor version upgrades may include behavior changes; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1777 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1777 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data