Quick answers
- Is CVE-2026-40116 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40116 being exploited in the wild.
- How severe is CVE-2026-40116?
- High severity, with a CVSS score of 7.5, published 9 April 2026.
- Which products and versions are affected?
- praisonai (PyPI) ECOSYSTEM:introduced=0,fixed=4.5.128.
- Is there a fix for CVE-2026-40116?
- Yes. praisonai (PyPI): upgrade to 4.5.128 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40116 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-40116?
- Check whether you run Praisonai or praisonai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- praisonai (PyPI): upgrade to 4.5.128 or later
pip install "praisonai>=4.5.128"
Technical details
The vulnerability exists in the `/media-stream` WebSocket endpoint within `src/praisonai/praisonai/api/call.py`. The endpoint fails to implement authentication middleware, Twilio request signature validation (X-Twilio-Signature), or connection/rate limits. Upon connection, the server automatically establishes an authenticated session with OpenAI's Realtime API using the host's `OPENAI_API_KEY`. An unauthenticated remote attacker can exploit this to forward arbitrary audio data to OpenAI, draining the victim's API credits. Furthermore, the lack of `ws_max_size` constraints and connection limits allows for memory exhaustion and Denial of Service (DoS). The issue is fixed in version 4.5.128.
Affected products
- MervinPraison PraisonAI < 4.5.128
Identifiers
- CVE-2026-40116
- GHSA-q5r4-47m9-5mc7
- PYSEC-2026-2920
Timeline
- 2026-04-09: patched: Fixed in version 4.5.128
- 2026-04-10: advisory