CVE-2025-32392: AutoGPT has a DoS vulnerability in LoopVideoBlock
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.
Security readout for executives and security teams
Plain-English summary
AutoGPT versions before 0.6.63 can let an unauthenticated network attacker trigger excessive video processing in LoopVideoBlock. Because loop counts are not limited, the system can create very large files and fill disk space, causing denial of service. Organizations running exposed AutoGPT workflows should treat this as urgent availability risk.
Executive priority
Prioritize remediation for any exposed or shared AutoGPT deployment because this flaw can directly disrupt service availability. Upgrade is the clearest remediation named by the source. This is not described as data theft or code execution, but disk exhaustion can still create operational outages.
Technical view
CVE-2025-32392 is a CWE-400 uncontrolled resource consumption issue in Significant-Gravitas AutoGPT before 0.6.63. LoopVideoBlock accepts user-controlled video looping or extension parameters without resource limits. Excessive looping can produce oversized output written to disk, exhausting storage. CVSS v4.0 score is 8.7 with network attack vector, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is most relevant where AutoGPT instances or workflows using LoopVideoBlock accept untrusted or internet-accessible input. The source identifies affected versions as AutoGPT before 0.6.63. If AutoGPT is internal-only and input is tightly controlled, practical exposure is lower but still depends on tenant and workflow trust boundaries.
Exploitation context
The advisory describes a denial-of-service condition from attacker-controlled loop counts causing disk exhaustion. The provided sources do not state active exploitation, public exploit availability, or CISA KEV listing. The attack does not require privileges or user interaction according to the CVSS vector.
Researcher notes
Evidence is limited to the CVE record and GitHub security advisory. The root issue is missing resource controls in LoopVideoBlock output generation. No exploit code, exploitation-in-the-wild claim, or additional affected products are provided in the supplied sources.
Mitigation direction
Upgrade AutoGPT to version 0.6.63 or later.
Restrict access to AutoGPT workflows accepting video input.
Limit untrusted use of LoopVideoBlock until upgraded.
Apply disk quotas and monitoring where feasible.
Review vendor advisory for any updated guidance.
Validation and detection
Inventory AutoGPT deployments and record installed versions.
Confirm any version before 0.6.63 is prioritized for remediation.
Identify workflows using LoopVideoBlock or video-processing input.
Check whether those workflows accept unauthenticated or untrusted input.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-400 · source CWE mapping
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.