CVE-2026-115419 (CVSS 8.1)

Description

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 state between callers. An authenticated remote user could read other tenants' conversation history and add persistent instructions that alter model behavior for subsequent callers via HTTP requests to the A2A endpoint using a different context_id. To mitigate this issue, users should upgrade to strands-agents 1.43.0 (Python) or @strands-agents/sdk 1.5.0 (TypeScript).

Is your site exposed to CVE-2026-115419?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

8.1

HIGH

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

EPSS — Exploit Prediction

0.0043

Probability of exploitation

0.37%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

Weakness Type (CWE)

CWE-488 CWE-488

References

Other References

https://aws.amazon.com/security/security-bulletins/2026-146-aws/ https://github.com/strands-agents/harness-sdk/security/advisories/GHSA-4v6f-7vjh-6x4m https://pypi.org/project/strands-agents/1.43.0/ https://www.npmjs.com/package/@strands-agents/sdk/v/1.5.0

Frequently Asked Questions

What is 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 state between callers. An authenticated remote user could read other tenants' conversation history and add persistent instructions that alter model behavior for subsequent callers via HTTP requests to the A2A endpoint using a different context_id. To mitigate this issue, users should upgrade to strands-agents 1.43.0 (Python) or @strands-agents/sdk 1.5.0 (TypeScript). It has a CVSS v3.1 base score of 8.1 (HIGH).

How severe is CVE-2026-115419? +

CVE-2026-115419 has a CVSS v3.1 score of 8.1 out of 10, rated HIGH. This is a high-severity vulnerability that should be prioritized for patching. The EPSS score is 0.0043, placing it in the 0th percentile for exploitation probability.

How do I check if I'm vulnerable to CVE-2026-115419? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2024-8314

An Incorrect Implementation of Authentication Algorithm and Exposure of Data Element to Wrong Ses-sion vulnerability in the session handling used …

CVE-2026-112921

Robots::Validate versions from 0.4.3 before 0.4.10 for Perl report clients as imposter robots when User-Agent matcher state carries over from …

CVE-2026-82806

Exposure of data element to wrong session vulnerability in Apache APISIX. This issue affects Apache APISIX: from 2.3.0 before 3.7.0. …

CVE-2026-111242

When MicroProfile JWT authentication is used for servlets that declare a run-as identity, the security state established for a request …

CVE-2026-111245

After a successful WS-Security UsernameToken authentication, the caller identity stays associated with the worker thread once the request completes when …

CVE-2026-82367

Exposure of Data Element to Wrong Session vulnerability in ash-project ash_graphql can deliver one subscription's resolved records to a different …