dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2025-32436

HIGH · 7.1 CVSS v4.0 Published 2026-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
AutoGPT is a workflow automation platform for creating, deploying, and managing continuous artificial intelligence agents. Prior to 0.6.63, `AddAudioToVideoBlock` will download and store the video and audio in a temporary directory without deleting before all noded are done. `StepThroughItemsBlock` can be used to iterate `MediaDurationBlock` multiple times. `StepThroughItemsBlock` does not limit the number of loops. In addition, `AddAudioToVideoBlock` does not limit the amount of disk space consumed in the current working directory and does not delete the video after outputing the result. When a malicious user chooses to screen shot many web pages, the disk space will eventually run out, causing a DoS. Version 0.6.63 patches the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

AutoGPT's `AddAudioToVideoBlock` downloads and stores video/audio files in temporary directories without proper cleanup, while `StepThroughItemsBlock` permits unlimited loop iterations. An attacker can repeatedly trigger media generation to exhaust disk space, causing denial of service.

MitigationUpgrade to AutoGPT version 0.6.63 or later, which implements proper temporary file cleanup, disk space limits, and loop iteration controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify AutoGPT version
    Check the installed AutoGPT version by examining the package.json, setup.py, or running 'pip show autogpt' or 'git describe --tags' if installed from source
    Affected if Version is older than 0.6.63 or version cannot be determined
  2. Locate temporary media files
    Search common temporary directories (system temp, /tmp, app-specific temp) for video/audio files created by AutoGPT. Run 'find /tmp -name "*.mp4" -o -name "*.mp3" -o -name "*.wav" -mtime -7' to find recently created media files
    Affected if Large numbers of unreferenced media files exist in temp directories indicating lack of cleanup
  3. Inspect AddAudioToVideoBlock usage
    Search project source code for imports and usage of AddAudioToVideoBlock class. Check logs or execution history for media generation operations
    Affected if AddAudioToVideoBlock has been invoked and temporary files remain after execution
  4. Check StepThroughItemsBlock configuration
    Review workflow or configuration files that define StepThroughItemsBlock usage. Look for loop definitions without explicit iteration limits
    Affected if StepThroughItemsBlock is configured with no maximum iteration count or unbounded item lists
  5. Monitor disk space during operation
    Observe disk usage before and after triggering media generation workflows. Use 'df -h' to check available space
    Affected if Disk space decreases significantly after repeated media generation operations

Environment is affected if running AutoGPT version below 0.6.63 and AddAudioToVideoBlock or StepThroughItemsBlock are in use with observable accumulation of temporary files or unbounded loops.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to AutoGPT version 0.6.63 or later, which implements proper temporary file cleanup, disk space limits, and loop iteration controls.

Recommended fix High confidence

0.6.63

  1. Upgrade AutoGPT to version 0.6.63 or later to resolve the uncontrolled resource consumption vulnerability in AddAudioToVideoBlock and StepThroughItemsBlock

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32436 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32436 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data