CVE-2025-32423: AutoGPT: There is a DoS vulnerability in ExtractTextInformationBlock
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 ExtractTextInformationBlock. 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.
Security readout for executives and security teams
Plain-English summary
AutoGPT versions before 0.6.32 can be pushed into extreme memory consumption by a low-privileged user. The reported example says 10 KB of input can drive about 50 GB of server memory use, causing denial of service. This is availability-focused, not data theft, and the vendor reports it fixed in 0.6.32.
Executive priority
Treat this as a near-term stability fix for exposed or shared AutoGPT deployments. It is not described as data compromise, but successful abuse can interrupt agent workflows and consume server resources quickly.
Technical view
CVE-2025-32423 affects Significant-Gravitas AutoGPT before 0.6.32 in ExtractTextInformationBlock. The issue is CWE-770: resource allocation without adequate limits. CVSS v4 is 5.3 with network attack vector, low complexity, low privileges, no user interaction, and low availability impact only.
Likely exposure
Exposure is likely limited to organizations running AutoGPT versions earlier than 0.6.32 where low-privileged users can submit workflow input reaching ExtractTextInformationBlock. No CPEs are provided in the source bundle, so product discovery may require package, image, or application inventory checks.
Exploitation context
The CVE is not listed as KEV, and the supplied sources do not state active exploitation. The public advisory describes a practical denial-of-service condition through input amplification, but no exploit status beyond that is provided.
Researcher notes
The strongest evidence is the GitHub advisory and CVE record. Affected scope is stated as AutoGPT before 0.6.32. The bundle does not provide vulnerable code details, proof-of-concept status, CPEs, or evidence of exploitation in the wild.
Mitigation direction
Upgrade AutoGPT to version 0.6.32 or later.
Restrict AutoGPT access to trusted users until upgraded.
Monitor AutoGPT hosts for abnormal memory growth and restarts.
Review the GitHub advisory for vendor-specific follow-up guidance.
Validation and detection
Inventory AutoGPT deployments and record exact running versions.
Flag any AutoGPT version earlier than 0.6.32 as affected.
Check whether users can reach workflows using ExtractTextInformationBlock.
Review monitoring for memory exhaustion around AutoGPT activity.
Confirm upgraded deployments report AutoGPT 0.6.32 or later.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.