# CVE-2025-32392: AutoGPT has a DoS vulnerability in LoopVideoBlock

> Attackers can exhaust disk space by specifying unlimited video loops in AutoGPT, causing a denial of service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jun 2026
- **Updated:** 18 Jun 2026
- **Also known as:** GHSA-267x-8jx3-gg6w

## What is CVE-2025-32392?

CVE-2025-32392 is a high-severity denial of service vulnerability in Significant-Gravitas AutoGPT, published on 18 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2025-32392?


## How do I fix CVE-2025-32392?

No fix has been published for CVE-2025-32392 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-32392 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32392 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32392 and fix it if it is affected.

What it is: CVE-2025-32392 is a high-severity denial of service vulnerability in Significant-Gravitas AutoGPT, published on 18 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32392 exists.

Affected product: Significant-Gravitas AutoGPT. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32392/ (Markdown: https://insights.sbomify.com/CVE-2025-32392/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32392
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32392
- OSV: https://osv.dev/vulnerability/CVE-2025-32392

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32392/
Summaries are generated and may contain mistakes; the official description above is the record.