Strands Agents Tools 0.8.6 Fixes Secret-Masking Bypass

P2 — VALIDATE AND UPDATEMedium · 5.9 (CVSS v4.0); 6.5 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

AWS bulletin 2026-154-AWS fixes CVE-2026-115415 in Strands Agents Tools before 0.8.6. Inventory agents that loaded the environment tool, upgrade or disable it, rotate credentials that could have been returned, validate agent behavior, and retain evidence.

Confirm Scope And Apply The Supported Remediation

What to do now: Inventory agents, applications and notebooks using strands-agents-tools, exact package and fork versions, environment-tool loading, accessible environment variables, execution identities, prompt sources, owners, logs, and deployment pipelines. Confirm that the affected environment tool was loaded and could receive untrusted prompts; do not infer credential disclosure solely from package presence, and do not assume masking protected earlier sessions. Upgrade to 0.8.6 or later, remove or disable the deprecated environment tool where possible, patch forks and derivative code, and rotate credentials present in environments of agents that loaded it. Confirm lockfiles and deployed versions, verify the model cannot disable masking, test operator controls, review agent traces and credential use where warranted, and retain package, rotation and change evidence.

Open the authoritative advisory

Last verified: 2026-10-29 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeStrands Agents Tools environment tool
Advisory2026-154-AWS / GHSA-qjx4-hg6g-2f34
CVECVE-2026-115415
Authoritative release date2026-10-28 19:30:00 UTC
Authority revision date2026-10-28 19:37:36.733 UTC
Affected versionsstrands-agents-tools 0.1.0 through releases before 0.8.6 when an agent loads the environment tool.
Fixed versionstrands-agents-tools 0.8.6 or later; the environment tool is deprecated in that release
CVSS base score5.9 (CVSS v4.0); 6.5 (CVSS v3.1)
CVSS severityMedium
Exploitation statusAWS does not state that this vulnerability is being maliciously exploited.; no exploitation claim is inferred.

What Changed

AWS fixed prompt-controlled secret masking that could let a crafted prompt make the environment tool return host environment variables, including cloud credentials and API keys, without operator consent.

What To Validate Now

  1. Inventory. Inventory agents, applications and notebooks using strands-agents-tools, exact package and fork versions, environment-tool loading, accessible environment variables, execution identities, prompt sources, owners, logs, and deployment pipelines.
  2. Establish applicability. Confirm that the affected environment tool was loaded and could receive untrusted prompts; do not infer credential disclosure solely from package presence, and do not assume masking protected earlier sessions.
  3. Remediate. Upgrade to 0.8.6 or later, remove or disable the deprecated environment tool where possible, patch forks and derivative code, and rotate credentials present in environments of agents that loaded it.
  4. Validate. Confirm lockfiles and deployed versions, verify the model cannot disable masking, test operator controls, review agent traces and credential use where warranted, and retain package, rotation and change evidence.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Credential rotation may affect running workloads and integrations. Preserve relevant agent traces before cleanup, coordinate rotations, and treat long-lived cloud or API credentials as higher-priority exposure.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.