Skip to content
Thursday, October 22, 2026AboutContactRSS
Vulnerabilities

AWS Security Bulletins: CVE-2026-78379 - Consent bypass in Strands Agents Tools python_repl tool

AWS Security Bulletins has published a new security advisory. Here is a summary and what to do.

AWS Security Bulletins: CVE-2026-78379 - Consent bypass in Strands Agents Tools python_repl tool
Illustration: Threat Times

Key points

  • New advisory from AWS Security Bulletins.
  • Review affected versions in the advisory.
  • Apply updates promptly.

AWS Security Bulletins published a security advisory titled “CVE-2026-78379 - Consent bypass in Strands Agents Tools python_repl tool”.

At a glance

Publisher
AWS Security Bulletins
CVEs
CVE-2026-78379

What the advisory says

Bulletin ID: 2026-089-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 08/25/2026 12:00 PM PDT Description: 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 python_repl tool, which executes Python code on the agent's host, and the batch tool, which invokes several other tools in a single call. Before executing code, python_repl prompts the operator for approval. We identified CVE-2026-78379, a consent bypass in the python_repl tool. Improper neutralization of input used for LLM prompting in the python_repl tool in Amazon Strands Agents Tools before 0.8.5 might allow remote actors to execute arbitrary Python code on the agent's host by bypassing the human consent gate, via a crafted prompt that forwards non_interactive_mode as a keyword

What should you do?

  • Read the full vendor advisory linked below and confirm whether you run affected versions.
  • Schedule the recommended update, prioritising internet-facing systems.
  • Watch for exploitation reports; unpatched edge devices are frequent targets.

What to do and how to stay safe: CVE-2026-78379

  • Vulnerability severity scores ignore your specific architecture and context.
  • Exploitability depends on network exposure and user behavior, not just code flaws.
  • Prioritization requires continuous asset inventory and threat intelligence alignment.

Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.

Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Sources

  1. AWS Security Bulletins advisory
Related articles