Skip to main content
VulnerabilityPublished

CVE-2026-24780: Significant-Gravitas AutoGPT · Incorrect Authorization

Affects Significant-Gravitas AutoGPTSource CVE Database V5

0

Public exploit available · CVSS 8.6 High : upgrade to 0.6.44 as a priority.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.6.44
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade AutoGPT and significant-gravitas/AutoGPT to 0.6.44.

Affected software

ProductAffectedFixed in
Significant-GravitasAutoGPTAffected
  • >=0.1.0 <0.6.44
Fixed in
  • 0.6.44
GitHubsignificant-gravitas/AutoGPTpkg:github/significant-gravitas/AutoGPTOther threatsAffected
  • <0.6.44
Fixed in
  • 0.6.44

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…