dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2025-32422

HIGH · 8.7 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 →
96/100
Remediation priority · Urgent
Remotely reachable No privileges 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, `StepThroughItemsBlock` can iterate all the contents in a list and send them to `FileStoreBlock` for downloading one by one. Although `FileStoreBlock` has access time limits for downloading files, `StepThroughItemsBlock` can be used to slowly iterate and download relatively small files (e.g., 100M) multiple times. `StepThroughItemsBlock` does not limit the number of loops. In addition, `FileStoreBlock` does not limit the amount of disk space consumed in the current working directory. When a malicious user chooses to download too many videos, 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

In AutoGPT before 0.6.63, the StepThroughItemsBlock component lacks loop iteration limits and can repeatedly invoke FileStoreBlock to download files. Combined with FileStoreBlock's absence of disk space consumption controls, an attacker can repeatedly download large files (e.g., videos) until disk storage is exhausted, causing denial of service.

MitigationUpgrade to version 0.6.63 or later, which implements loop iteration limits on StepThroughItemsBlock and disk space quota controls on FileStoreBlock to prevent unbounded file downloads.

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
None
Authentication
X
User interaction
None
Scope
X

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/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. Determine installed AutoGPT version
    Run 'pip show autogpt' or check the version file in the AutoGPT installation directory (e.g., pyproject.toml, setup.py, or version.txt in the project root)
    Affected if Version is below 0.6.63 (e.g., 0.6.0 through 0.6.62)
  2. Identify if StepThroughItemsBlock is in use
    Search the codebase for imports or references to 'StepThroughItemsBlock' in Python files or configuration files within the AutoGPT installation directory
    Affected if StepThroughItemsBlock is present and actively used in any workflow or agent configuration
  3. Verify FileStoreBlock configuration
    Search for FileStoreBlock references in the codebase and check if it is configured to handle file downloads from external sources
    Affected if FileStoreBlock is enabled and allows arbitrary file downloads without quota restrictions
  4. Check for unbounded iteration patterns
    Inspect any configurations or scripts that use StepThroughItemsBlock to process lists of items, looking for the absence of explicit loop limits or iteration caps
    Affected if No iteration limit or max_loop parameter is set on StepThroughItemsBlock usage
  5. Monitor disk space consumption
    Use system commands (df -h on Linux/macOS or Get-PSDrive on Windows) to observe if AutoGPT process or its working directory shows unusually rapid disk space depletion
    Affected if Disk space decreases rapidly while AutoGPT is running and processing items through StepThroughItemsBlock with FileStoreBlock downloads

A user is affected if they run AutoGPT version below 0.6.63 AND have StepThroughItemsBlock processing lists in combination with FileStoreBlock enabled for external file downloads, resulting in uncontrolled disk consumption.

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 version 0.6.63 or later, which implements loop iteration limits on StepThroughItemsBlock and disk space quota controls on FileStoreBlock to prevent unbounded file downloads.

Recommended fix High confidence

0.6.63

  1. 1. Identify the currently installed AutoGPT version using pip show autogpt or checking your project's requirements.txt
  2. 2. Upgrade AutoGPT to version 0.6.63 or later using: pip install --upgrade autogpt>=0.6.63
  3. 3. Verify the upgrade was successful by running: pip show autogpt and confirming the version number

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32422 — 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-32422 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