VulnerabilityPublished 5 Feb 2026

CVE-2025-32393: Significant-Gravitas AutoGPT · Unthrottled Resource Allocation

Affects Significant-Gravitas AutoGPTSource CVE Database V5

Not known to be exploited · CVSS 8.7 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Significant-GravitasAutoGPT	Affected =< autogpt-platform-beta-v0.6.32	Fixed in–

AI-suggested

Immediately upgrade all AutoGPT deployments to autogpt-platform-beta-v0.6.32 or later, which contains the patch that enforces resource limits during XML parsing.
Implement network-level filtering or input validation to restrict or sanitize RSS feed URLs and XML content before processing, blocking feeds with suspiciously deep nesting or excessive size.
Deploy runtime monitoring and alerting on resource usage metrics (memory, CPU) for AutoGPT processes to detect abnormal spikes indicative of exploitation attempts.
Use containerization or sandboxing to isolate AutoGPT instances, limiting the impact of potential DoS attacks on other systems.
Establish rate limiting on API endpoints that accept feed URLs to reduce the risk of automated exploitation.
Conduct regular security assessments and penetration testing focused on AI automation components to identify similar resource exhaustion vulnerabilities.
Maintain up-to-date threat intelligence feeds to monitor for emerging exploits targeting AutoGPT or related AI platforms.

Description

CVE-2025-32393 is a high-severity denial-of-service (DoS) vulnerability in Significant-Gravitas AutoGPT versions prior to autogpt-platform-beta-v0.6.32. The flaw exists in the ReadRSSFeedBlock component, where the feedparser.parser processes user-supplied XML feeds without limits on parsing time or resource allocation. An attacker can craft deeply nested or complex XML payloads that exhaust memory resources, causing the application to crash or become unresponsive. This vulnerability requires no authentication or user interaction and can be exploited remotely over the network. Although no known exploits are currently in the wild, the CVSS 8.7 score reflects the ease of exploitation and high impact on availability. The issue has been patched in version 0.

Impact

For European organizations, the primary impact of CVE-2025-32393 is the potential disruption of AI-driven automation workflows that utilize AutoGPT, particularly those involving RSS feed ingestion or similar XML parsing tasks. A successful attack can cause service outages, impacting business continuity and operational efficiency. Organizations in sectors such as finance, manufacturing, telecommunications, and media—where AI automation is increasingly integrated—may experience degraded service availability or downtime. This can lead to financial losses, reputational damage, and reduced trust in AI systems. Additionally, the denial-of-service condition could be leveraged as part of a broader attack strategy to distract or disable critical AI services. Since the vulnerability does not compromise confidentiality or integrity, the main concern is availability. The lack of authentication or user interaction requirements makes it easier for attackers to exploit remotely, increasing the threat surface for European enterprises using vulnerable versions of AutoGPT.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Feb 2026, 07:20 UTC

WeaknessesCWE-770

Technical details

References

Community reviews

Related threats