dbcve.org
CWE-405Weakness · CWE-405

CVE-2025-32394

MEDIUM · 5.3 CVSS v4.0 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click 8 weeks old

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.32, there is a DoS vulnerability in AITextSummarizerBlock. Malicious users can amplify their input. For example, if a malicious user inputs 10K of content, the server will consume 50G of memory, eventually causing memory resources to be exhausted, resulting in DoS. This vulnerability is fixed in 0.6.32.

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 prior to 0.6.32 contain a Denial of Service vulnerability in the AITextSummarizerBlock component where malicious input amplification causes severe memory exhaustion - as demonstrated by 10KB of input consuming 50GB of server memory.

MitigationUpgrade to AutoGPT version 0.6.32 or later which contains the fix. Consider implementing input size limits or validation as a defense-in-depth measure.

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:L/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 installed AutoGPT version
    Locate the AutoGPT installation directory and check the version file or package metadata (common locations include version.py, __init__.py, pyproject.toml, or package.json depending on installation method)
    Affected if The version number is lower than 0.6.32 (e.g., 0.6.31, 0.6.0, etc.)
  2. Confirm AITextSummarizerBlock component is present
    Search the codebase for the AITextSummarizerBlock class or module definition - look in source files containing 'summarizer' or 'AITextSummarizerBlock' in the plugin or block directories
    Affected if The AITextSummarizerBlock component exists in the installation and is not patched or removed
  3. Check if summarization features are enabled
    Inspect the configuration files or runtime settings that enable or disable AI text processing blocks, particularly summarization functionality
    Affected if The summarization feature is active or can be invoked through the application interface or API
  4. Monitor memory behavior with test input
    If the component is present and enabled, test the summarization function with a modest input size (a few KB) while monitoring system memory consumption
    Affected if Memory consumption grows disproportionately to input size (e.g., a 10KB input causes multi-GB memory usage)

You are affected if AutoGPT version is below 0.6.32 and the AITextSummarizerBlock summarization feature is accessible and exhibits abnormal memory amplification when processing text inputs.

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.32 or later which contains the fix. Consider implementing input size limits or validation as a defense-in-depth measure.

Recommended fix High confidence

0.6.32

  1. 1. Check the current installed version of AutoGPT by running: pip show autogpt or checking your project's version file
  2. 2. If the version is below 0.6.32, backup your current installation and any custom configurations
  3. 3. Upgrade AutoGPT to version 0.6.32 or later using: pip install --upgrade autogpt>=0.6.32 or follow your project's specific upgrade procedure
  4. 4. Verify the upgrade was successful by running: pip show autogpt and confirming the version number
  5. 5. Test that the AITextSummarizerBlock functionality works correctly with the new version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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