Service interruption via unbounded container log growth
Published May 13, 2026 · Updated May 13, 2026
Resource exhaustion in Significant Gravitas AutoGPT before 0.6.32 allows local users to interrupt service by generating excessive logs. Docker Compose services and Python logging handlers write container and application output without rotation or size caps, allowing persistent growth to consume the host disk. Exploitation requires access that can drive a self-hosted container deployment to emit sustained logs; the bounded consequence is disk exhaustion and service interruption.
Summary
What happened
Resource exhaustion in Significant Gravitas AutoGPT before 0.6.32 allows local users to interrupt service by generating excessive logs. Docker Compose services and Python logging handlers write container and application output without rotation or size caps, allowing persistent growth to consume the host disk. Exploitation requires access that can drive a self-hosted container deployment to emit sustained logs; the bounded consequence is disk exhaustion and service interruption.
The record
- CVE
- CVE-2025-32425
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- Significant Gravitas
- Product
- AutoGPT
- Classifications
- CWE-770, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.6.32
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo