dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2026-33232

HIGH · 7.5 CVSS v3.1 Published 2026-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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. Versions 0.4.2 through 0.6.51 are vulnerable to an unauthenticated Denial of Service (DoS) through the server due to uncontrolled disk space consumption. The download_agent_file endpoint creates persistent temporary files for every request but fails to delete them after they are served. An unauthenticated attacker can repeatedly call this endpoint to exhaust the server's disk space, causing the database or other system services to fail due to "No space left on device" errors, rendering the entire AutoGPT Platform backend unavailable to all users. This issue has been patched in version 0.6.52.

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 versions 0.4.2-0.6.51 contain an unauthenticated DoS vulnerability in the download_agent_file endpoint, which creates persistent temporary files for each request but fails to delete them after serving. Attackers can repeatedly call this endpoint to exhaust disk space, causing the database and system services to fail with 'No space left on device' errors.

MitigationUpgrade to version 0.6.52 or later to patch this vulnerability. Additionally, implement proper temporary file cleanup in the download_agent_file endpoint to prevent file system exhaustion.

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
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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
    Locate the AutoGPT installation and check its version file or package.json for the installed version number
    Affected if The installed version falls between 0.4.2 and 0.6.51 inclusive
  2. Confirm download_agent_file endpoint exists
    Inspect the codebase or API routes configuration to verify the download_agent_file endpoint is defined and accessible
    Affected if The endpoint exists in the codebase and is exposed via the API router
  3. Check for temporary file accumulation
    Monitor the server temporary file directory (commonly /tmp or a temp folder within the AutoGPT installation) for files related to agent downloads that are not being cleaned up
    Affected if Temporary download files accumulate and persist after requests complete
  4. Verify unauthenticated access
    Test if the download_agent_file endpoint can be accessed without authentication by sending a request without valid credentials
    Affected if The endpoint accepts requests without requiring authentication

If AutoGPT versions 0.4.2-0.6.51 are running with the download_agent_file endpoint exposed and unauthenticated, the environment is vulnerable to disk space exhaustion via uncleaned temporary files

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.52 or later to patch this vulnerability. Additionally, implement proper temporary file cleanup in the download_agent_file endpoint to prevent file system exhaustion.

Recommended fix High confidence

Upgrade to version 0.6.52 or later

  1. 1. Backup your current AutoGPT installation and any important data
  2. 2. Identify your current AutoGPT version (check package.json, requirements.txt, or the running application)
  3. 3. If using a package manager (npm, pip, docker), update to version 0.6.52 or later: for npm use 'npm install [email protected]', for pip use 'pip install autogpt==0.6.52', or pull the 0.6.52 docker image
  4. 4. If using a git-based installation, checkout the release tag v0.6.52 or later
  5. 5. After upgrading, restart the AutoGPT service
  6. 6. Verify the fix by checking that temporary files in the download_agent_file endpoint are properly cleaned up after serving requests
  7. 7. Monitor disk space usage to confirm the resource consumption issue is resolved
Caveat Review release notes for version 0.6.52 to check for any breaking changes between your current version and the fixed release

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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