CVE-2026-45023: Significant-Gravitas AutoGPT · Unthrottled Resource Allocation
Affects Significant-Gravitas AutoGPTSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium : upgrade to 0.6.59 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.6.59
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade AutoGPT and significant-gravitas/AutoGPT to 0.6.59.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Significant-GravitasAutoGPT | Affected
| Fixed in
|
GitHubsignificant-gravitas/AutoGPTpkg:github/significant-gravitas/AutoGPTOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade AutoGPT to version 0.6.59 or later, where this vulnerability is fixed. No other official remediation or temporary fixes are documented. Users should ensure that all API calls are routed through the graph execution path that enforces credit checks. Patch status is confirmed fixed in 0.6.59.
Description
AutoGPT is a workflow automation platform for creating, deploying, and managing continuous artificial intelligence agents. Prior to 0.6.59, POST /api/blocks/{block_id}/execute endpoint executes blocks without consuming any credits, regardless of the user's balance. The credit check that exists in the graph execution path (manager.py) is never reached when blocks are called directly via the external API, allowing unlimited free execution of all blocks. This vulnerability is fixed in 0.6.59.