(AutoGPT), Log Size Unbounded, CVE-2025-32425 (Medium)

Listen to this Post

How the CVE works:

AutoGPT deploys AI agents in Docker containers. The execution process writes logs to stdout/stderr, which Docker captures as container logs. Prior to version 0.6.32, AutoGPT imposed no limit on log file size. Each user interaction and workflow step generates log entries. Under normal load, logs rotate or are truncated, but AutoGPT lacked any rotation or size cap. When many users access the system concurrently, log volume grows linearly. Logs accumulate on the server’s disk partition. Without a limit, a single container can write gigabytes or terabytes. Disk space eventually reaches 100% usage. The operating system can no longer write temporary files or new logs. Services depending on disk I/O start failing. The AutoGPT platform becomes unresponsive. Docker daemon may also stall due to disk exhaustion. This leads to a Denial of Service (DoS) condition. The attack requires no special privileges—only repeated requests. An attacker can trigger DoS by sending high volumes of traffic. The issue is exacerbated in container mode where logs persist indefinitely. AutoGPT does not enforce log rotation policies by default. The fix in version 0.6.32 introduces log size limits and rotation. No workaround existed before the patch. The vulnerability is local to the host filesystem but remotely exploitable.

dailycve form:

Platform: AutoGPT platform
Version: prior 0.6.32
Vulnerability: Unbounded container logs
Severity: Medium
date: May 26 2026

Prediction: Patch May 13 2026

What Undercode Say:

Analytics:

Simulate log exhaustion by writing unlimited entries
for i in {1..1000000}; do echo "CVE-2025-32425 test log line $i" >> /var/log/autogpt.log; done
Check disk usage to monitor DoS impact
df -h /var/lib/docker/containers/
Detect uncontrolled log growth in real time
watch -n 1 'du -sh /var/lib/docker/containers//.log'
Rotate logs manually as a temporary mitigation (prior to patch)
logrotate -f /etc/logrotate.d/autogpt

Exploit:

Send high-frequency HTTP requests to any AutoGPT endpoint that triggers agent execution. Each request writes to stdout, captured by Docker. Use `ab -n 100000 -c 100 http://target/execute` to flood. Monitor disk with `df -huntil 100% full. Platform becomes unresponsive.
<h2 style="color: blue;">Protection from this CVE:</h2>
Upgrade to AutoGPT version 0.6.32 or later. If upgrade is impossible, implement external log rotation: set Docker log driver to "json-file" with
–log-opt max-size=10m –log-opt max-file=3`. Alternatively, mount logs to tmpfs or bind with size quota. Use `logrotate` to compress and prune daily.

Impact:

Denial of Service via disk exhaustion. Platform becomes completely unavailable. No data loss but service disruption. Recovery requires manual log deletion and container restart. Attackers with minimal access can crash the system.

🎯Let’s Practice Exploiting & Learn Patching For Free:

Sources:

Reported By: nvd.nist.gov
Extra Source Hub:
Undercode

🎓 Live Courses & Certifications:

Join Undercode Academy for Verified Certifications

🚀 Request a Custom Project:

Secure, high-velocity infrastructure and disruptive technological engineering. Contact our engineering team for high-tier development and proprietary systems:
[email protected]

🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]

💬 Whatsapp | 💬 Telegram

📢 Follow DailyCVE & Stay Tuned:

𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin Featured Image

Scroll to Top