Summary
AutoGPT is Vulnerable to RCE via Disabled Block Execution
Impact
Any user who can create an account on AutoGPT Platform can achieve full Remote Code Execution on the backend server.
This allows:
- Complete server compromise
- Access to all user data, credentials, and API keys stored in the database
- Access to environment variables (cloud credentials, secrets)
- Lateral movement to connected infrastructure (Redis, PostgreSQL, cloud services)
- Persistent backdoor installation
Attack requirements:
- Create a free account on the platform (default self-hosted enables signup; hosted deployments may disable signup, requiring an existing account)
- Know the disabled block's UUID (hardcoded in public source code:
45e78db5-03e9-447f-9395-308d712f5f08)
Why the disabled flag exists but fails:
- Block listing correctly filters disabled blocks (users don't see them in UI)
- Execution endpoints bypass this check entirely
- The UUID is static and publicly known from the open-source codebase
Severity note: CVSS assumes the default self-hosted configuration where signup is enabled (low-privilege authentication is easy to obtain). If signup is disabled in a hosted deployment, likelihood is lower, but impact remains critical once any authenticated account exists.
A fix is available, but was not published to the PyPI registry at time of publication: 0.6.44
Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
In the interim: Never evaluate untrusted input as code. Use sandboxed evaluation environments if dynamic execution is required.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-24780? CVE-2026-24780 is a high-severity code injection vulnerability in agpt (pip), affecting versions <= 0.2.2. No fixed version is listed yet. Untrusted input is evaluated as executable code within the application's runtime environment.
- Which versions of agpt are affected by CVE-2026-24780? agpt (pip) versions <= 0.2.2 is affected.
- Is there a fix for CVE-2026-24780? No fixed version is listed for CVE-2026-24780 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is CVE-2026-24780 exploitable, and should I be worried? Whether CVE-2026-24780 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-24780 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-24780? No fixed version is listed yet. In the interim: Never evaluate untrusted input as code. Use sandboxed evaluation environments if dynamic execution is required.