dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2025-32424

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, ScreenshotWebPageBlock will store the captured screenshots in a temporary directory. `StepThroughItemsBlock` can be used to iterate `ScreenshotWebPageBlock` multiple times. `StepThroughItemsBlock` does not limit the number of loops. In addition, `ScreenshotWebPageBlock` does not limit the amount of disk space consumed in the current working directory. 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 · moderate confidence

AutoGPT's ScreenshotWebPageBlock stores captured screenshots in a temporary directory without enforcing disk space limits. When combined with StepThroughItemsBlock, which permits unlimited iterations, a malicious user can trigger excessive screenshot captures that exhaust available disk space, causing denial of service.

MitigationUpgrade to version 0.6.63 or later. Alternatively, implement disk space quotas and iteration limits on ScreenshotWebPageBlock and StepThroughItemsBlock respectively, and monitor disk usage.

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. Identify AutoGPT installation and version
    Run 'pip show autogpt' or check the project version file (e.g., pyproject.toml, version.txt) to determine the installed version
    Affected if Version is lower than 0.6.63 (e.g., 0.6.62, 0.6.0, or any pre-0.6.63 release)
  2. Locate ScreenshotWebPageBlock configuration
    Search project configuration files (e.g., config.yaml, config.json, settings.py) or plugin directory for 'ScreenshotWebPageBlock' or 'screenshot' block definitions
    Affected if ScreenshotWebPageBlock is present and enabled in the configuration
  3. Locate StepThroughItemsBlock configuration
    Search configuration files or plugin directory for 'StepThroughItemsBlock' or 'step_through' block definitions
    Affected if StepThroughItemsBlock is present and enabled in the configuration
  4. Check for disk space quota enforcement
    Inspect configuration files and runtime settings for disk quota, storage limit, or temp directory size constraints related to screenshot storage
    Affected if No disk space quota or storage limit is configured for the screenshot temporary directory
  5. Check for iteration limits on StepThroughItemsBlock
    Examine StepThroughItemsBlock configuration for max_iterations, loop_limit, or iteration caps
    Affected if No iteration limit is configured (unlimited iterations allowed)

Environment is affected if running AutoGPT version below 0.6.63 with both ScreenshotWebPageBlock and StepThroughItemsBlock enabled, and no disk space quotas or iteration limits are configured.

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. Alternatively, implement disk space quotas and iteration limits on ScreenshotWebPageBlock and StepThroughItemsBlock respectively, and monitor disk usage.

Recommended fix High confidence

0.6.63

  1. 1. Identify the currently running AutoGPT version using `pip show autogpt` or checking your deployment manifests
  2. 2. If running a version prior to 0.6.63, upgrade to version 0.6.63 or later
  3. 3. For pip installations: run `pip install --upgrade autogpt` or `pip install autogpt==0.6.63`
  4. 4. Verify the upgrade was successful by checking the version again
  5. 5. Consider implementing disk monitoring alerts as a defense-in-depth measure

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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