vciy

CVE-2026-1777

INDEX BUILT · 2026-10-18

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Cleartext transmission of sensitive materials in aws/sagemaker-python-sdk

CVE-2026-17773 of 4 sources documented this
18

rank 18 = 0 + 18 + 0 + 0 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00517  ·  without this subject the record ranks 18

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.2, from the CNA  ·  without this subject the record ranks 0

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 18

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges  ·  without this subject the record ranks 18

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 18

Hindsight · the state

0.00517EPSSNOT IN KEVas of 2026-10-18
Severity7.2 HIGHreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2026-02-03, 239 days at 0.01, as of 2026-09-30. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running AWS SageMaker Python SDK? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Watch AWS SageMaker Python SDK

Set up a watchlist (free with an account: one stack of three products)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · high privileges required · no user interaction · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-319 Cleartext Transmission of Sensitive Informationreceipt
Published consequencesCWE-319: Integrity, Confidentiality: Read Application Data, Modify Files or Directories; Integrity, Confidentiality: Read Application Data, Modify Files or Directories, Othercwe-consequences@4.20

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in3.2.0; 2.256.0receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA7.2 HIGHreceipt
Exploit probability0.00517 · top 57% of all CVEsreceipt
Assigned byAMZNreceipt
Recorded changes9 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Affected productAWS SageMaker Python SDKreceipt
Fixed in3.2.0; 2.256.0receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$25,800over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$25,800 = $4.99M incident cost x 1 exposure x 0.00517 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Did this affect your environment?Answering needs an account.

Attack path

Network requestrequires high privilegesAWS SageMaker Python SDKCWE-319 weaknessFull compromise (C/I/A)C:H / I:H / A:Hexploits CWE-319data compromise

What it is stated by the CNA

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. receipt

NVD's analysis a second authority

weakness
CWE-319
also scored by
8.5 CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X · 7.2…

check it yourself aws.amazon.com github.com github.com github.com receipt

Movement the material steps

3 Feb 20260.00011
15 Jun 20260.00455 · scoring model v2026.06.15
30 Sep 20260.00517
Show all 9 observations
3 Feb 20260.00011
4 Feb 20260.00013
6 Mar 20260.00014
26 Apr 20260.00019
4 Jun 20260.00022
15 Jun 20260.00455
1 Sep 20260.00473
28 Sep 20260.00484
30 Sep 20260.00517

9 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00517Published2026-02-02Index as of2026-09-30

The record had been public for 7 months when this index was last written.

Published 2026-02-02 receipt · Index as of 2026-09-30 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2026-1777.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.