GHSA-4V6F-7VJH-6X4M

Vulnerability from github – Published: 2026-10-23 20:48 – Updated: 2026-10-23 20:48
VLAI
Summary
Strands Agents SDK: Exposure of data element to wrong session in the A2A Server
Details

Summary
Strands Agents SDK is an open-source SDK, available for Python (strands-agents) and TypeScript (@strands-agents/sdk), for building and running AI agents. An issue exists where, under certain circumstances, the Agent2Agent (A2A) server shares conversation history across callers with different context_id values, allowing one caller to read and influence another caller's session.

Impact
The A2A server did not properly isolate conversation state between callers. In multi-tenant deployments, an authenticated remote user could access another caller's conversation history or influence model behavior for other callers (CWE-488: Unintended Disclosure of Data Element to Wrong Session). This affects any deployment where an A2A server is reachable by more than one user or tenant.

Impacted versions:
strands-agents (Python): all versions containing the multiagent.a2a module, < 1.43.0
@strands-agents/sdk (TypeScript): < 1.5.0

Patches
This issue has been addressed in strands-agents version 1.43.0 and @strands-agents/sdk version 1.5.0. The A2A server now uses an agent factory so conversation state is isolated per A2A context_id. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.

Workarounds
There is no workaround that fully addresses this issue in affected versions. Until you upgrade, do not expose an A2A server to more than one user or tenant. If multiple callers need access, run a separate A2A server instance for each user or tenant.

References
If you have any questions or comments about this advisory, we ask that you contact AWS Security via our vulnerability reporting page or directly via email to aws-security@amazon.com. Please do not create a public GitHub issue.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "strands-agents"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.43.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "npm",
        "name": "@strands-agents/sdk"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.5.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-115419"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-488"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-10-23T20:48:29Z",
    "nvd_published_at": "2026-10-22T21:17:17Z",
    "severity": "HIGH"
  },
  "details": "**Summary**  \nStrands Agents SDK is an open-source SDK, available for Python (strands-agents) and TypeScript (@strands-agents/sdk), for building and running AI agents. An issue exists where, under certain circumstances, the Agent2Agent (A2A) server shares conversation history across callers with different context\\_id values, allowing one caller to read and influence another caller\u0027s session.  \n  \n**Impact**  \nThe A2A server did not properly isolate conversation state between callers. In multi-tenant deployments, an authenticated remote user could access another caller\u0027s conversation history or influence model behavior for other callers (CWE-488: Unintended Disclosure of Data Element to Wrong Session). This affects any deployment where an A2A server is reachable by more than one user or tenant.  \n  \n**Impacted versions:**  \nstrands-agents (Python): all versions containing the multiagent.a2a module, \u003c 1.43.0  \n@strands-agents/sdk (TypeScript): \u003c 1.5.0  \n  \n**Patches**  \nThis issue has been addressed in strands-agents version 1.43.0 and @strands-agents/sdk version 1.5.0. The A2A server now uses an agent factory so conversation state is isolated per A2A context\\_id. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.  \n  \n**Workarounds**  \nThere is no workaround that fully addresses this issue in affected versions. Until you upgrade, do not expose an A2A server to more than one user or tenant. If multiple callers need access, run a separate A2A server instance for each user or tenant.  \n  \n**References**  \nIf you have any questions or comments about this advisory, we ask that you contact AWS Security via our [vulnerability reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.",
  "id": "GHSA-4v6f-7vjh-6x4m",
  "modified": "2026-10-23T20:48:29Z",
  "published": "2026-10-23T20:48:29Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/strands-agents/harness-sdk/security/advisories/GHSA-4v6f-7vjh-6x4m"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-115419"
    },
    {
      "type": "WEB",
      "url": "https://github.com/strands-agents/harness-sdk/pull/2628"
    },
    {
      "type": "WEB",
      "url": "https://github.com/strands-agents/harness-sdk/pull/2696"
    },
    {
      "type": "WEB",
      "url": "https://github.com/strands-agents/harness-sdk/commit/398343faad0e485f2e441dab70355c9a52382537"
    },
    {
      "type": "WEB",
      "url": "https://github.com/strands-agents/harness-sdk/commit/403d87847e738e1c73909858d989cedcb67f0afa"
    },
    {
      "type": "WEB",
      "url": "https://github.com/strands-agents/harness-sdk/commit/f8ba9376fe4b8330d526b6480b47c4440150e0cd"
    },
    {
      "type": "WEB",
      "url": "https://aws.amazon.com/security/security-bulletins/2026-146-aws"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/strands-agents/harness-sdk"
    },
    {
      "type": "WEB",
      "url": "https://github.com/strands-agents/harness-sdk/releases/tag/python/v1.43.0"
    },
    {
      "type": "WEB",
      "url": "https://github.com/strands-agents/harness-sdk/releases/tag/typescript/v1.5.0"
    },
    {
      "type": "WEB",
      "url": "https://pypi.org/project/strands-agents/1.43.0"
    },
    {
      "type": "WEB",
      "url": "https://www.npmjs.com/package/@strands-agents/sdk/v/1.5.0"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Strands Agents SDK: Exposure of data element to wrong session in the A2A Server"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.