CVE-2026-24780

GHSA-r277-3xc5-c79v HIGH
Published January 29, 2026
CISO Take

A critical RCE vulnerability in AutoGPT Platform allows any authenticated user—including self-registered attackers in default Supabase deployments—to execute arbitrary Python code on your server by invoking a disabled block that bypasses authorization checks. Patch immediately to v0.6.44+, disable public signup, and rotate all credentials and API keys stored in or accessible from the platform. If self-hosting AutoGPT in production, treat this as an active incident until patched and audited.

Affected Systems

Package Ecosystem Vulnerable Range Patched
agpt pip <= 0.2.2 No patch
autogpt_platform No patch

Severity & Risk

CVSS 3.1
8.8 / 10
EPSS
0.1%
chance of exploitation in 30 days
KEV Status
Not in KEV
Sophistication
Trivial

Recommended Action

  1. 1. PATCH: Upgrade to autogpt-platform-beta-v0.6.44 or later immediately—no safe workaround exists that preserves full functionality. 2. QUICK WIN: Disable Supabase public signup to require attackers to have a pre-existing account while patching is underway. 3. NETWORK: Restrict AutoGPT backend API access to trusted networks; place behind VPN or IP allowlist if public exposure is not required. 4. ROTATE CREDENTIALS: After patching, rotate all API keys, LLM provider tokens (OpenAI, Anthropic), and integration credentials stored in or accessible from the platform—assume compromise if unpatched instances were internet-facing. 5. DETECT: Search web and API access logs for requests to block execution endpoints (external/v1/routes.py L79-93 and features/v1.py L1408-1424) using the BlockInstallationBlock UUID; unexpected executions by non-admin users are IOCs. 6. AUDIT FILESYSTEM: Review server filesystem for unexpected Python files written by the platform post-exploit. 7. POST-PATCH: Audit user accounts for unauthorized self-registrations and revoke as needed.

Classification

Compliance Impact

This CVE is relevant to:

EU AI Act
Art. 15 - Accuracy, robustness and cybersecurity Article 15 - Accuracy, Robustness and Cybersecurity
ISO 42001
A.6.2.2 - AI System Security A.6.2.4 - AI system access control A.8.4 - AI System Lifecycle Security A.9.4 - AI system security
NIST AI RMF
GOVERN 1.1 - Policies, Processes and Procedures for AI Risk GOVERN 1.7 - Processes and procedures are in place for decommissioning and phasing out AI systems safely MANAGE 2.2 - Mechanisms to Respond to and Recover from AI Risks
OWASP LLM Top 10
LLM06 - Excessive Agency LLM07 - Insecure Plugin Design LLM08 - Excessive Agency

Technical Details

NVD Description

AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. Prior to autogpt-platform-beta-v0.6.44, AutoGPT Platform's block execution endpoints (both main web API and external API) allow executing blocks by UUID without checking the `disabled` flag. Any authenticated user can execute the disabled `BlockInstallationBlock`, which writes arbitrary Python code to the server filesystem and executes it via `__import__()`, achieving Remote Code Execution. In default self-hosted deployments where Supabase signup is enabled, an attacker can self-register; if signup is disabled (e.g., hosted), the attacker needs an existing account. autogpt-platform-beta-v0.6.44 contains a fix.

Exploitation Scenario

An attacker identifies a publicly accessible self-hosted AutoGPT Platform instance. In the default configuration with Supabase signup enabled, the attacker self-registers a free account in seconds. Using the authenticated session, the attacker calls the block execution API endpoint with the well-known UUID of the disabled BlockInstallationBlock—a UUID discoverable directly from the open-source codebase on GitHub without any prior system access. The attacker embeds a Python reverse shell or credential-harvesting payload; the platform writes this code to the server filesystem and executes it via Python's __import__() function, achieving OS-level code execution. The attacker then exfiltrates all stored LLM provider API keys, cloud credentials, and agent workflow configurations, establishes persistence, and pivots into connected downstream services. The entire attack requires no AI/ML expertise—only basic HTTP API interaction and knowledge of the public GitHub repository.

CVSS Vector

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

Timeline

Published
January 29, 2026
Last Modified
February 17, 2026
First Seen
January 29, 2026