Memory exhaustion via unbounded WSGI request bodies
Published Apr 9, 2026 · Updated Apr 9, 2026
Resource exhaustion in PraisonAI before 4.5.128 allows local users to crash the recipe registry via oversized POST bodies. The WSGI handler in server.py trusts Content-Length, reads that many bytes into one in-memory object, and multipart parsing creates further copies without a size ceiling. Default no-token mode and loopback binding expose the service to unauthenticated local processes; memory exhaustion can terminate the registry and disrupt recipe operations.
Summary
What happened
Resource exhaustion in PraisonAI before 4.5.128 allows local users to crash the recipe registry via oversized POST bodies. The WSGI handler in server.py trusts Content-Length, reads that many bytes into one in-memory object, and multipart parsing creates further copies without a size ceiling. Default no-token mode and loopback binding expose the service to unauthenticated local processes; memory exhaustion can terminate the registry and disrupt recipe operations.
The record
- CVE
- CVE-2026-40115
- Published
- Apr 9, 2026
- Updated
- Apr 9, 2026
- Vendor
- PraisonAI
- Product
- PraisonAI
- Classifications
- CWE-770, T1499.003
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 2026CVE publishedPublication date reported by the CVE source.
- Apr 9, 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=< 4.5.128
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
- Vendor oversized recipe-upload PoCproof of concept · demonstrated
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