CVE-2026-41496: PraisonAI: SQL Injection via unvalidated `table_prefix` in 9 conversation store backends (incomplete fix for CVE-2026-40315)
PraisonAI is a multi-agent teams system. Prior to praisonai version 4.6.9 and praisonaiagents version 1.6.9, the fix for CVE-2026-40315 added input validation to SQLiteConversationStore only. Nine sibling backends — MySQL, PostgreSQL, async SQLite/MySQL/PostgreSQL, Turso, SingleStore, Supabase, SurrealDB — pass tableprefix straight into f-string SQL. Same root cause, same code pattern, same exploitation. 52 unvalidated injection points across the codebase. postgres.py additionally accepts an unvalidated schema parameter used directly in DDL. This issue has been patched in praisonai version 4.6.9 and praisonaiagents version 1.6.9.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41496?
CVE-2026-41496 has been classified as a high severity vulnerability due to its potential for SQL injection leading to unauthorized data access.
How do I fix CVE-2026-41496?
To fix CVE-2026-41496, upgrade to PraisonAI version 4.6.9 or higher and PraisonAI agents version 1.6.9 or higher.
What types of attacks does CVE-2026-41496 enable?
CVE-2026-41496 enables SQL injection attacks through unvalidated user input, potentially leading to data breaches.
What versions are affected by CVE-2026-41496?
CVE-2026-41496 affects PraisonAI versions prior to 4.6.9 and PraisonAI agents prior to 1.6.9.
Is CVE-2026-41496 part of a series of vulnerabilities?
Yes, CVE-2026-41496 is related to an incomplete fix for CVE-2026-40315.