CVE-2026-24780: CWE-863: Incorrect Authorization in Significant-Gravitas AutoGPT
CVE-2026-24780 is a high-severity vulnerability in Significant-Gravitas AutoGPT versions prior to 0. 6. 44 that allows authenticated users to execute arbitrary Python code remotely. The flaw arises because the platform's block execution endpoints do not verify the 'disabled' flag on blocks, enabling execution of a disabled block that writes and runs arbitrary code on the server. In self-hosted deployments with enabled signup, attackers can self-register to exploit this; otherwise, an existing account is required. This vulnerability leads to remote code execution (RCE) with high impact on confidentiality, integrity, and availability. The issue is fixed in version 0. 6. 44. European organizations using vulnerable AutoGPT versions should urgently update and restrict signup options to mitigate risk.
AI Analysis
Technical Summary
The vulnerability CVE-2026-24780 affects Significant-Gravitas AutoGPT, a platform for managing continuous AI agents automating workflows. Versions from 0.1.0 up to but not including 0.6.44 have a critical authorization flaw in their block execution endpoints (both main web API and external API). These endpoints allow execution of blocks identified by UUID without verifying whether the block is disabled. Specifically, the disabled 'BlockInstallationBlock' can be executed by any authenticated user. This block writes arbitrary Python code to the server filesystem and executes it using Python's __import__() function, resulting in remote code execution (RCE). In default self-hosted deployments where Supabase signup is enabled, attackers can self-register and exploit this vulnerability without prior credentials. In hosted environments where signup is disabled, attackers must have valid accounts. The vulnerability stems from CWE-863 (Incorrect Authorization), CWE-94 (Improper Control of Generation of Code), and CWE-276 (Incorrect Default Permissions). The CVSS 4.0 score is 8.6 (high severity) reflecting network attack vector, low attack complexity, no user interaction, and high impact on confidentiality, integrity, and availability. No known exploits are reported in the wild yet. The vendor fixed the issue in autogpt-platform-beta-v0.6.44 by enforcing authorization checks on block execution endpoints and disabling execution of dangerous blocks.
Potential Impact
For European organizations, this vulnerability poses a significant risk if they deploy vulnerable versions of AutoGPT, especially in self-hosted environments with open signup. Successful exploitation allows attackers to execute arbitrary code on the server, potentially leading to full system compromise, data theft, manipulation of AI workflows, disruption of business processes, and lateral movement within networks. Confidentiality is at risk due to unauthorized data access; integrity is compromised by arbitrary code execution; availability can be impacted by destructive payloads or denial-of-service conditions. Organizations relying on AutoGPT for critical automation or AI-driven decision-making could face operational outages or reputational damage. The ease of exploitation in self-hosted setups with enabled signup increases the threat surface. Even hosted environments are at risk if attackers gain legitimate credentials. The lack of known exploits currently provides a window for proactive mitigation before widespread attacks occur.
Mitigation Recommendations
European organizations should immediately upgrade all AutoGPT deployments to version 0.6.44 or later to apply the official patch that enforces proper authorization checks. For self-hosted instances, disable Supabase signup or restrict it to trusted users only to prevent unauthorized registrations. Implement strict access controls and monitor authentication logs for suspicious activity. Employ network segmentation to isolate AutoGPT servers from critical infrastructure. Use runtime application self-protection (RASP) or endpoint detection and response (EDR) tools to detect anomalous code execution behaviors. Regularly audit AI workflow configurations and disable any unnecessary or potentially dangerous blocks. Conduct penetration testing focusing on API endpoints to verify authorization enforcement. Maintain up-to-date backups and incident response plans tailored for AI platform compromises. Finally, educate developers and administrators about secure deployment practices for AI automation platforms.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2026-24780: CWE-863: Incorrect Authorization in Significant-Gravitas AutoGPT
Description
CVE-2026-24780 is a high-severity vulnerability in Significant-Gravitas AutoGPT versions prior to 0. 6. 44 that allows authenticated users to execute arbitrary Python code remotely. The flaw arises because the platform's block execution endpoints do not verify the 'disabled' flag on blocks, enabling execution of a disabled block that writes and runs arbitrary code on the server. In self-hosted deployments with enabled signup, attackers can self-register to exploit this; otherwise, an existing account is required. This vulnerability leads to remote code execution (RCE) with high impact on confidentiality, integrity, and availability. The issue is fixed in version 0. 6. 44. European organizations using vulnerable AutoGPT versions should urgently update and restrict signup options to mitigate risk.
AI-Powered Analysis
Technical Analysis
The vulnerability CVE-2026-24780 affects Significant-Gravitas AutoGPT, a platform for managing continuous AI agents automating workflows. Versions from 0.1.0 up to but not including 0.6.44 have a critical authorization flaw in their block execution endpoints (both main web API and external API). These endpoints allow execution of blocks identified by UUID without verifying whether the block is disabled. Specifically, the disabled 'BlockInstallationBlock' can be executed by any authenticated user. This block writes arbitrary Python code to the server filesystem and executes it using Python's __import__() function, resulting in remote code execution (RCE). In default self-hosted deployments where Supabase signup is enabled, attackers can self-register and exploit this vulnerability without prior credentials. In hosted environments where signup is disabled, attackers must have valid accounts. The vulnerability stems from CWE-863 (Incorrect Authorization), CWE-94 (Improper Control of Generation of Code), and CWE-276 (Incorrect Default Permissions). The CVSS 4.0 score is 8.6 (high severity) reflecting network attack vector, low attack complexity, no user interaction, and high impact on confidentiality, integrity, and availability. No known exploits are reported in the wild yet. The vendor fixed the issue in autogpt-platform-beta-v0.6.44 by enforcing authorization checks on block execution endpoints and disabling execution of dangerous blocks.
Potential Impact
For European organizations, this vulnerability poses a significant risk if they deploy vulnerable versions of AutoGPT, especially in self-hosted environments with open signup. Successful exploitation allows attackers to execute arbitrary code on the server, potentially leading to full system compromise, data theft, manipulation of AI workflows, disruption of business processes, and lateral movement within networks. Confidentiality is at risk due to unauthorized data access; integrity is compromised by arbitrary code execution; availability can be impacted by destructive payloads or denial-of-service conditions. Organizations relying on AutoGPT for critical automation or AI-driven decision-making could face operational outages or reputational damage. The ease of exploitation in self-hosted setups with enabled signup increases the threat surface. Even hosted environments are at risk if attackers gain legitimate credentials. The lack of known exploits currently provides a window for proactive mitigation before widespread attacks occur.
Mitigation Recommendations
European organizations should immediately upgrade all AutoGPT deployments to version 0.6.44 or later to apply the official patch that enforces proper authorization checks. For self-hosted instances, disable Supabase signup or restrict it to trusted users only to prevent unauthorized registrations. Implement strict access controls and monitor authentication logs for suspicious activity. Employ network segmentation to isolate AutoGPT servers from critical infrastructure. Use runtime application self-protection (RASP) or endpoint detection and response (EDR) tools to detect anomalous code execution behaviors. Regularly audit AI workflow configurations and disable any unnecessary or potentially dangerous blocks. Conduct penetration testing focusing on API endpoints to verify authorization enforcement. Maintain up-to-date backups and incident response plans tailored for AI platform compromises. Finally, educate developers and administrators about secure deployment practices for AI automation platforms.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-01-26T21:06:47.869Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 697b9f9cac06320222a8a3d2
Added to database: 1/29/2026, 5:57:48 PM
Last enriched: 1/29/2026, 6:12:08 PM
Last updated: 1/29/2026, 7:36:46 PM
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-25068: CWE-129 Improper Validation of Array Index in ALSA Project alsa-lib
MediumCVE-2026-1610: Hard-coded Credentials in Tenda AX12 Pro V2
CriticalCVE-2026-1457: CWE-121 Stack-based Buffer Overflow in TP-Link Systems Inc. VIGI C485 V1
HighCVE-2026-1453: CWE-306 Missing Authentication for Critical Function in KiloView Encoder Series E1 hardware Version 1.4
CriticalCVE-2026-1601: Command Injection in Totolink A7000R
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.