Quick answers
- Is CVE-2026-40315 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40315 being exploited in the wild.
- How severe is CVE-2026-40315?
- Critical severity, with a CVSS score of 9.8, published 14 April 2026.
- Which products and versions are affected?
- praisonai (PyPI) ECOSYSTEM:introduced=0,fixed=4.5.133.
- Is there a fix for CVE-2026-40315?
- Yes. praisonai (PyPI): upgrade to 4.5.133 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40315 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-40315?
- 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.133 or later
pip install "praisonai>=4.5.133"
Technical details
A SQL injection vulnerability exists in PraisonAI's SQLiteConversationStore due to improper neutralization of the 'table_prefix' configuration value. The software uses Python f-strings to concatenate this prefix directly into SQL table identifiers, which cannot be safely parameterized in standard SQL queries. An attacker capable of providing a malicious configuration (via YAML or dictionary input) can inject arbitrary SQL fragments, such as UNION SELECT statements. This allows for unauthorized access to internal SQLite metadata tables (like sqlite_master) and the ability to tamper with query results. The issue is fixed in version 4.5.133.
Affected products
- MervinPraison PraisonAI < 4.5.133
Identifiers
- CVE-2026-40315
- GHSA-x783-xp3g-mqhp
- PYSEC-2026-2925
Timeline
- 2026-04-09: patched: Version 4.5.133 released
- 2026-04-10: advisory: GitHub Advisory published
- 2026-04-14: other: NVD publication date