Vulnerability feed

CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run Oct 26 04:05 UTC

Critical in the last 24 hours

1602 in 30 days

Newly known exploited

In the last 24 hours, CISA KEV and vendor reports

Sources checked

Every hour, see the list

New in the last 24 hours

154-74% vs 7-day avg of 597

2 critical, 44 high, 61 medium, 27 low

Expand	Severity	Score	Advisory	Title	Source	Flags	Published
	Critical	9.4	CVE-2026-112408	Missing verification of source of a communication channel in the default_bucket() function in Amazon SageMaker Python SDK V3 before 3.10.0 and V2 before 2.257.3 might allow... AWS, AmazonAWS Amazon SageMaker Python SDK, Amazon SageMaker Python SDK	NVD		Oct 21 20:17 UTC
CVE-2026-112408Missing verification of source of a communication channel in the default_bucket() function in Amazon SageMaker Python SDK V3 before 3.10.0 and V2 before 2.257.3 might allow... Executive summary Amazon SageMaker Python SDK, an open-source library used to train and deploy machine learning models on Amazon SageMaker, has a flaw that could let an outside party take control of a SageMaker execution environment and obtain IAM credentials. The advisory describes this as an important issue requiring attention. AWS recommends upgrading to Amazon SageMaker Python SDK 2.257.3 (V2) or 3.10.0 (V3), and says any forked or derivative code should also be patched. Technical summary The flaw is a missing verification of bucket ownership in the default_bucket() function, where the SDK uses a predictably named Amazon S3 bucket without checking that the caller's AWS account owns it. A remote actor who creates that bucket first could achieve code execution in a remote SageMaker execution environment and obtain IAM credentials. Impacted versions are V2 before 2.257.3 and V3 from 3.0.0 before 3.10.0, and the fixed versions are 2.257.3 (V2) and 3.10.0 (V3). The workaround is to explicitly pass an S3 bucket the account owns through the default_bucket parameter of sagemaker.Session or the SDK configuration file, and not to rely on the auto-generated bucket name. The advisory does not state a CVSS score, whether the issue is exploited in the wild, or any detection guidance. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from aws.amazon.com/security/security-bulletins/2026-142-aws Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityHigh How it is exploited Attack vector Network Attack complexity Low Attack requirements Present Privileges required None User interaction None CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:N/SA:N/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 Affects AWS Amazon AWS Amazon SageMaker Python SDK Amazon SageMaker Python SDK NIST National Vulnerability DatabasePublished Oct 21, 2026 20:17 UTC Read the advisory

Example	Finds
	Every word appears somewhere: title, summaries, IDs, vendor, or product
	An exact phrase
	One vendor. product: for a product, vp: for either
	Commas mean any of them, in every field
	Severity: critical, high, medium, low, or unknown
	CVSS score, with >, >=, <, or <=
	A score range
	Known exploited. is:kev works too, and kev:no leaves them out
	One source, by name
	Confidentiality impact: high, low, none, or any (low or high)
	Integrity and availability work the same way
	An advisory or CVE ID, or part of one
	A minus sign leaves out whatever the term matches

Vulnerability feed

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee