CVE-2025-32425: Significant-Gravitas AutoGPT · Unthrottled Resource Allocation
Affects Significant-Gravitas AutoGPTSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 0.6.32 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.6.32
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 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.32.
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.32 or later, where the issue is fixed by implementing log size limits. Since the vendor advisory indicates the fix is included in version 0.6.32, applying this update is the recommended remediation. No other mitigation or temporary workaround is specified.
Description
AutoGPT is a platform that allows users to create, deploy, and manage continuous artificial intelligence agents that automate complex workflows. In AutoGPT, the execution process is recorded to the console (stdout/stderr), and deployed in container mode, which is automatically captured by Docker and stored as "container logs". However, prior to 0.6.32, there is no limit on the log size when the container is deployed. When the number of user accesses is too large, the log on the server disk will be too large, causing disk resource exhaustion and eventually causing DoS.autogpt-platform-beta-v0.6.32 fixes the issue.
References
- github.com/Significant-Gravitas/AutoGPT/security/advisories/GHSA-vw3v-whvp-33v5 (opens in a new tab)
- github.com/Significant-Gravitas/AutoGPT/commit/57a06f70883ce6be18738c6ae8bb41085c71e266 (opens in a new tab)
- github.com/Significant-Gravitas/AutoGPT/blob/62361ccc48327b3124549543b45d933d16f622d2/autogpt_platform/autogpt_libs/autogpt_libs/logging/config.py (opens in a new tab)
- github.com/Significant-Gravitas/AutoGPT/blob/62361ccc48327b3124549543b45d933d16f622d2/autogpt_platform/docker-compose.platform.yml (opens in a new tab)