Vulnerability feed
CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run
| Expand | Severity |
Score |
Advisory |
Title |
Source |
Flags |
Published |
|---|---|---|---|---|---|---|---|
| High | 8.6 | CVE-2026-115419 |
The A2A server component in Amazon Strands Agents SDK for Python before 1.43.0 and Amazon Strands Agents SDK for TypeScript before 1.5.0 does not properly isolate conversation...
AWS, AmazonAWS strands-agents, AWS strands-agents/sdk, Amazon Strands Agents SDK for Python, Amazon Strands Agents SDK for TypeScript, Amazon Strands Agents SDK A2A Server
|
NVD | |||
|
CVE-2026-115419The A2A server component in Amazon Strands Agents SDK for Python before 1.43.0 and Amazon Strands Agents SDK for TypeScript before 1.5.0 does not properly isolate conversation...
Executive summaryAmazon's Strands Agents SDK, available for Python and TypeScript, has a flaw in its Agent2Agent server component that can let one caller see another caller's conversation data. The advisory says an authenticated user could reach other callers' conversation history or influence model behavior in multi-tenant deployments. The vendor recommends upgrading to Python version 1.43.0 or TypeScript version 1.5.0 and has no full workaround for affected versions. Technical summaryThe A2A server did not properly isolate conversation state between callers, which is an improper isolation or cross-session data exposure issue. An authenticated remote user could access another caller's conversation history or influence model behavior for other callers in multi-tenant deployments. Affected versions are strands-agents (Python) versions containing the multiagent.a2a module before 1.43.0, and @strands-agents/sdk (TypeScript) before 1.5.0. Fixed versions are strands-agents 1.43.0 and @strands-agents/sdk 1.5.0, where conversation state is now isolated per A2A context_id. The advisory states there is no workaround that fully addresses the issue; until upgrade, it advises not exposing an A2A server to more than one user or tenant, or running a separate server instance per user or tenant. No detection guidance or exploitation status is stated in the advisory. 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-146-aws Impact if exploitedConfidentialityHigh IntegrityHigh AvailabilityNone
How it is exploited
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/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 AffectsAWSAmazonAWS strands-agentsAWS strands-agents/sdkAmazon Strands Agents SDK for PythonAmazon Strands Agents SDK for TypeScriptAmazon Strands Agents SDK A2A Server
NIST National Vulnerability DatabasePublished
Read the advisory
|
|||||||
| Medium | 6.3 | CVE-2026-115416 |
Incorrect authorization checks in Amazon Athena engine version 3 query processing could have allowed an authenticated user to read AWS account identifiers and SQL statement...
AWS, AmazonAWS Amazon Athena, Amazon Athena
|
NVD | |||
|
CVE-2026-115416Incorrect authorization checks in Amazon Athena engine version 3 query processing could have allowed an authenticated user to read AWS account identifiers and SQL statement...
Executive summaryAn authorization flaw in Amazon Athena engine version 3 could have let a signed-in user see AWS account identifiers and SQL statement text from other AWS accounts. AWS rates it as Important (requires attention) and says query results and data stored in Amazon S3 or other data sources were not accessible through this issue. AWS fixed the issue on October 7, 2026, and says no customer action is required. Technical summaryThe advisory describes incorrect authorization checks in Amazon Athena engine version 3 query processing, which is an information disclosure issue. An authenticated user could read AWS account identifiers and SQL statement text query metadata from other AWS accounts, but query results and data in Amazon S3 or other sources were not accessible. The impacted version is listed as Amazon Athena engine version 3, and AWS remediated the issue on October 7, 2026. No fixed build number or specific fixed version string is stated beyond that date, and no workarounds are available. The advisory gives no CVSS score, exploitation status, or detection guidance, and states none of these. 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-144-aws Impact if exploitedConfidentialityNone IntegrityNone AvailabilityNone
How it is exploited
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/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
NIST National Vulnerability DatabasePublished
Read the advisory
|
|||||||
| 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 | |||
|
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 summaryAmazon 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 summaryThe 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 exploitedConfidentialityHigh IntegrityHigh AvailabilityHigh
How it is exploited
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 AffectsAWSAmazonAWS Amazon SageMaker Python SDKAmazon SageMaker Python SDK
NIST National Vulnerability DatabasePublished
Read the advisory
|
|||||||
| Critical | 9.0 | CVE-2026-112380 |
Missing authorization in the WhatsApp group channel in Kiro Crew might allow a remote actor who is a member of an operator-configured WhatsApp group to control the operator's...
AmazonAmazon Kiro Crew
|
NVD | |||
|
CVE-2026-112380Missing authorization in the WhatsApp group channel in Kiro Crew might allow a remote actor who is a member of an operator-configured WhatsApp group to control the operator's...
From the advisoryMissing authorization in the WhatsApp group channel in Kiro Crew might allow a remote actor who is a member of an operator-configured WhatsApp group to control the operator's other agent sessions and execute arbitrary commands on the host running Kiro Crew via messages sent to the group. To remediate this issue, users should upgrade to version 0.7.2. Impact if exploitedConfidentialityHigh IntegrityHigh AvailabilityHigh
How it is exploited
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/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 Affects
NIST National Vulnerability DatabasePublished
Read the advisory
|
|||||||
| Medium | 6.0 | CVE-2026-110310 |
A remote user who can read encrypted objects in the S3 bucket can force a padding downgrade by altering the padding scheme recorded in an object's metadata to legacy PKCS#1 v1.5
AmazonAmazon.Extensions.S3.Encryption
|
NVD | |||
|
CVE-2026-110310A remote user who can read encrypted objects in the S3 bucket can force a padding downgrade by altering the padding scheme recorded in an object's metadata to legacy PKCS#1 v1.5
From the advisoryA remote user who can read encrypted objects in the S3 bucket can force a padding downgrade by altering the padding scheme recorded in an object's metadata to legacy PKCS#1 v1.5. Since this padding scheme is susceptible to the well-known Bleichenbacher attack, the user can use a PKCS#1 v1.5 padding oracle to recover the RSA-wrapped envelope key and decrypt the object. To remediate this issue, we recommend that users upgrade to version 3.2.2 or 4.0.3. The 1.x and 2.x lines will not be patched, users of those lines need to migrate to 3.2.2 or 4.0.3. Impact if exploitedConfidentialityHigh IntegrityNone AvailabilityNone
How it is exploited
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/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
NIST National Vulnerability DatabasePublished
Read the advisory
|
|||||||
| High | 8.7 | CVE-2026-104020 |
Uncontrolled recursion in the Ion reader in Amazon Ion Python before 0.15.0 might allow a remote unauthenticated actor to crash the application using the library, resulting in...
AmazonAmazon ion-python
|
NVD | |||
|
CVE-2026-104020Uncontrolled recursion in the Ion reader in Amazon Ion Python before 0.15.0 might allow a remote unauthenticated actor to crash the application using the library, resulting in...
From the advisoryUncontrolled recursion in the Ion reader in Amazon Ion Python before 0.15.0 might allow a remote unauthenticated actor to crash the application using the library, resulting in a denial of service, via a crafted, deeply nested Ion value. To remediate this issue, users should upgrade to version 0.15.0 or later. Impact if exploitedConfidentialityNone IntegrityNone AvailabilityHigh
How it is exploited
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/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
NIST National Vulnerability DatabasePublished
Read the advisory
|
|||||||