CVE-2025-32392: Significant-Gravitas AutoGPT · Uncontrolled Resource Consumption
Affects Significant-Gravitas AutoGPTSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 0.6.63 soon.
Data as of 1 Nov 2026, 22:57 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.6.63
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Jun 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 1 Nov 2026.
What to do
Upgrade AutoGPT and significant-gravitas/AutoGPT to 0.6.63.
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.63 or later, where this vulnerability is patched. There is no indication of alternative mitigations or temporary fixes. Users should apply the official update to prevent exploitation.
Description
AutoGPT is a workflow automation platform for creating, deploying, and managing continuous artificial intelligence agents. Prior to 0.6.63, AutoGPT's LoopVideoBLock allows users to input a video file and process the video, such as looping it 5 times or extending the time, and finally writing it to disk. However, there is no limit on the resources that can be allocated during execution. For example, the number of loops is user-controllable and unlimited. When a malicious attacker loops too many times, the generated video is too large, and after writing it to disk, the disk space is exhausted, eventually causing DoS. Version 0.6.63 patches the issue.