dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-15746

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Strands Agents is an open-source Python SDK for building and running AI agents. The strands-agents-tools package provides pre-built tools for use with the SDK, including the elasticsearch_memory tool for agent memory storage. We identified CVE-2026-15746, a server-side request forgery (SSRF) issue in the elasticsearch_memory tool. The tool exposed its connection parameters (es_url, cloud_id, api_key) as fields the large language model (LLM) could control through the tool schema. When a caller omitted the api_key parameter, the tool fell back to the operator's ELASTICSEARCH_API_KEY environment variable and sent it to whichever host the LLM specified. A crafted prompt could cause the tool to connect to a threat-actor-controlled server and disclose the operator's Elasticsearch API key in the Authorization header. We recommend you upgrade to strands-agents-tools version 0.7.0 or later. As a precautionary measure, we recommend all operators rotate their ELASTICSEARCH_API_KEY, even if there is no indication the credential was exposed.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a server-side request forgery (SSRF) vulnerability in the elasticsearch_memory tool of strands-agents-tools. The tool exposed connection parameters (es_url, cloud_id, api_key) that the LLM could control through the tool schema. When api_key was omitted, the tool fell back to the ELASTICSEARCH_API_KEY environment variable and sent it to whatever host the LLM specified, allowing a crafted prompt to exfiltrate the Elasticsearch API key to a threat actor-controlled server.

MitigationUpgrade to strands-agents-tools version 0.7.0 or later to fix the SSRF vulnerability. As a precautionary measure, rotate the ELASTICSEARCH_API_KEY credential even if no compromise is indicated.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed strands-agents-tools version
    Run `pip show strands-agents-tools` or check your dependency lock file for the strands-agents-tools version number
    Affected if The installed version is below 0.7.0 (the fixed release)
  2. Verify the ELASTICSEARCH_API_KEY environment variable is set
    Check if the ELASTICSEARCH_API_KEY environment variable exists in your runtime environment using `echo $ELASTICSEARCH_API_KEY` or inspect your environment configuration
    Affected if The ELASTICSEARCH_API_KEY environment variable is present and populated with a valid credential
  3. Confirm the elasticsearch_memory tool is enabled
    Inspect your strands-agents-tools configuration or code that initializes the agent tools to determine if elasticsearch_memory is included in the active tool list
    Affected if The elasticsearch_memory tool is loaded and available to the LLM
  4. Review recent network activity for suspicious outbound connections
    Inspect network logs, proxy logs, or audit trails for outbound connections from the agent process to unknown or external hosts that could indicate key exfiltration
    Affected if There are outbound connections from the agent to hosts other than the intended Elasticsearch endpoint

You are affected if strands-agents-tools version is below 0.7.0, the elasticsearch_memory tool is enabled, and the ELASTICSEARCH_API_KEY environment variable is set with a valid credential.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to strands-agents-tools version 0.7.0 or later to fix the SSRF vulnerability. As a precautionary measure, rotate the ELASTICSEARCH_API_KEY credential even if no compromise is indicated.

Recommended fix High confidence

strands-agents-tools version 0.7.0

  1. Check your currently installed version of strands-agents-tools by running: pip show strands-agents-tools
  2. Upgrade to version 0.7.0 or later using: pip install --upgrade strands-agents-tools>=0.7.0
  3. Verify the upgrade was successful by running: pip show strands-agents-tools and confirming the version number
  4. As a precautionary measure, rotate your ELASTICSEARCH_API_KEY environment variable credential even if there is no indication of exposure
Caveat Review the strands-agents-tools changelog for version 0.7.0 to check for any breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15746 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data