# CVE-2026-24780: AutoGPT is Vulnerable to RCE via Disabled Block Execution

> Authenticated users can execute disabled blocks to inject and run arbitrary Python code, leading to remote code execution on the server.

- **Severity:** High 8.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** GHSA-r277-3xc5-c79v, PYSEC-2026-1078

## What is CVE-2026-24780?

CVE-2026-24780 is a high-severity code injection vulnerability in Significant-Gravitas AutoGPT, published on 29 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-863 (Incorrect Authorization), CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2026-24780?

3 open source packages ship an affected version, including agpt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `agpt` | PyPI | All versions to 0.2.2 | None |
| `agpt` | PyPI | All versions to 0.2.2 | None |
| `agpt` | PyPI | All versions to 0.2.2 | None |

Products: Agpt Autogpt Platform.

## How do I fix CVE-2026-24780?

No fix has been published for CVE-2026-24780 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24780 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24780 exists.

## Other vulnerabilities in Significant-Gravitas AutoGPT

- [CVE-2026-26020](https://insights.sbomify.com/CVE-2026-26020/): AutoGPT Affected by Remote Code Execution via Dynamic Module Import in Block Loading (__import__) (critical 9.4)
- [CVE-2025-62615](https://insights.sbomify.com/CVE-2025-62615/): AutoGPT has SSRF vulnerability in ReadRSSFeedBlock (critical 9.3)
- [CVE-2025-62616](https://insights.sbomify.com/CVE-2025-62616/): AutoGPT has SSRF vulnerability in SendDiscordFileBlock (critical 9.3)
- [CVE-2025-1040](https://insights.sbomify.com/CVE-2025-1040/): Server-Side Template Injection (SSTI) in significant-gravitas/autogpt (high 8.8)
- [CVE-2025-32393](https://insights.sbomify.com/CVE-2025-32393/): AutoGPT has a DoS vulnerability in ReadRSSFeedBlock (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24780 and fix it if it is affected.

What it is: CVE-2026-24780 is a high-severity code injection vulnerability in Significant-Gravitas AutoGPT, published on 29 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24780 exists.

Affected packages and fixed versions:
- agpt (PyPI): affected all versions up to 0.2.2; no fix listed
- agpt (PyPI): affected all versions up to 0.2.2; no fix listed
- agpt (PyPI): affected all versions up to 0.2.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24780/ (Markdown: https://insights.sbomify.com/CVE-2026-24780/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24780
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24780
- OSV: https://osv.dev/vulnerability/CVE-2026-24780

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24780/
Summaries are generated and may contain mistakes; the official description above is the record.