Quick answers
- Is CVE-2026-34934 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34934 being exploited in the wild.
- How severe is CVE-2026-34934?
- Critical severity, with a CVSS score of 9.8, published 3 April 2026.
- Which products and versions are affected?
- praisonai (PyPI) ECOSYSTEM:introduced=0,fixed=4.5.90.
- Is there a fix for CVE-2026-34934?
- Yes. praisonai (PyPI): upgrade to 4.5.90 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34934 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-34934?
- 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.90 or later
pip install "praisonai>=4.5.90"
Technical details
A second-order SQL injection vulnerability exists in PraisonAI's SQLAlchemy data layer. The 'get_all_user_threads' function in 'src/praisonai/praisonai/ui/sql_alchemy.py' constructs raw SQL queries using Python f-strings to include thread IDs previously stored in the database. An attacker can first call 'update_thread' to store a malicious SQL payload as a 'thread_id'. When 'get_all_user_threads' is subsequently called, the unescaped payload is concatenated into an 'IN' clause, allowing for arbitrary SQL execution. This can result in full database exfiltration or modification. The vulnerability is resolved in version 4.5.90 by properly parameterizing queries.
Affected products
- MervinPraison PraisonAI < 4.5.90
Identifiers
- CVE-2026-34934
- GHSA-9cq8-3v94-434g
- PYSEC-2026-470
Timeline
- 2026-03-31: advisory: Vendor advisory published on GitHub
- 2026-04-03: disclosed: CVE published to NVD
- 2026-04-03: patched: Fix released in version 4.5.90