CVE-2026-40115: CWE-770: Allocation of Resources Without Limits or Throttling in MervinPraison PraisonAI
PraisonAI is a multi-agent teams system. Prior to 4.5.128, the WSGI-based recipe registry server (server.py) reads the entire HTTP request body into memory based on the client-supplied Content-Length header with no upper bound. Combined with authentication being disabled by default (no token configured), any local process can send arbitrarily large POST requests to exhaust server memory and cause a denial of service. The Starlette-based server (serve.py) has RequestSizeLimitMiddleware with a 10MB limit, but the WSGI server lacks any equivalent protection. This vulnerability is fixed in 4.5.128.
AI Analysis
Technical Summary
PraisonAI's WSGI-based recipe registry server (server.py) prior to version 4.5.128 does not impose any limit on the size of HTTP request bodies it reads into memory, relying solely on the client-supplied Content-Length header. With authentication disabled by default, this allows any local process to send arbitrarily large POST requests, leading to memory exhaustion and denial of service. The Starlette-based server (serve.py) mitigates this with a 10MB request size limit via RequestSizeLimitMiddleware, but the WSGI server lacks equivalent throttling. The vulnerability is addressed in version 4.5.128.
Potential Impact
An attacker with local access can cause a denial of service by exhausting server memory through sending large POST requests to the vulnerable WSGI-based server. There is no impact on confidentiality or integrity. The vulnerability does not require user interaction and has low attack complexity but requires local access.
Mitigation Recommendations
Upgrade PraisonAI to version 4.5.128 or later, where this vulnerability is fixed by adding request size limits to the WSGI-based server. Until upgraded, restrict local access to the server to trusted users only to prevent exploitation. Patch status is not explicitly stated but the vendor fixed the issue in version 4.5.128.
CVE-2026-40115: CWE-770: Allocation of Resources Without Limits or Throttling in MervinPraison PraisonAI
Description
PraisonAI is a multi-agent teams system. Prior to 4.5.128, the WSGI-based recipe registry server (server.py) reads the entire HTTP request body into memory based on the client-supplied Content-Length header with no upper bound. Combined with authentication being disabled by default (no token configured), any local process can send arbitrarily large POST requests to exhaust server memory and cause a denial of service. The Starlette-based server (serve.py) has RequestSizeLimitMiddleware with a 10MB limit, but the WSGI server lacks any equivalent protection. This vulnerability is fixed in 4.5.128.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
PraisonAI's WSGI-based recipe registry server (server.py) prior to version 4.5.128 does not impose any limit on the size of HTTP request bodies it reads into memory, relying solely on the client-supplied Content-Length header. With authentication disabled by default, this allows any local process to send arbitrarily large POST requests, leading to memory exhaustion and denial of service. The Starlette-based server (serve.py) mitigates this with a 10MB request size limit via RequestSizeLimitMiddleware, but the WSGI server lacks equivalent throttling. The vulnerability is addressed in version 4.5.128.
Potential Impact
An attacker with local access can cause a denial of service by exhausting server memory through sending large POST requests to the vulnerable WSGI-based server. There is no impact on confidentiality or integrity. The vulnerability does not require user interaction and has low attack complexity but requires local access.
Mitigation Recommendations
Upgrade PraisonAI to version 4.5.128 or later, where this vulnerability is fixed by adding request size limits to the WSGI-based server. Until upgraded, restrict local access to the server to trusted users only to prevent exploitation. Patch status is not explicitly stated but the vendor fixed the issue in version 4.5.128.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-09T01:41:38.537Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69d843751cc7ad14da3fb568
Added to database: 4/10/2026, 12:25:25 AM
Last enriched: 4/17/2026, 12:02:27 PM
Last updated: 5/25/2026, 12:55:03 AM
Views: 70
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.