Executive Summary

CVE-2026-41496 is a SQL injection vulnerability in the PraisonAI software affecting multiple conversation store backends including MySQL, PostgreSQL, async SQLite/MySQL/PostgreSQL, Turso, SingleStore, Supabase, and SurrealDB.

The issue arises because these backends accept a `table_prefix` parameter directly into SQL queries using f-strings without proper validation or sanitization, creating 52 injection points. Additionally, the PostgreSQL backend accepts an unvalidated `schema` parameter used in DDL operations.

This vulnerability allows attackers to inject malicious SQL code through externally controlled inputs such as multi-tenant configurations, API requests, or user-editable files. While a previous fix addressed this issue only for the SQLite backend, the other backends remained vulnerable until patched in version 4.6.9 of PraisonAI and version 1.6.9 of praisonaiagents.

Useful 0 Not Useful 0

Impact Analysis

Exploitation of this vulnerability can allow attackers to execute arbitrary SQL commands on the affected databases.

• Attackers can gain full read access to sensitive data.
• Attackers can modify or delete data, compromising data integrity.
• Attackers can perform destructive operations such as dropping tables.

Overall, this can lead to significant confidentiality and integrity breaches in your database systems.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by checking if your PraisonAI deployment uses any of the nine affected backends (MySQL, PostgreSQL, async SQLite/MySQL/PostgreSQL, Turso, SingleStore, Supabase, SurrealDB) with externally controlled table_prefix or schema parameters that are not properly validated.

Detection involves reviewing configuration files, API inputs, or multi-tenant settings for unvalidated table_prefix or schema values that could be exploited.

You can also attempt to detect SQL injection vulnerabilities by testing injection payloads in these parameters, such as using inputs like: x'; DROP TABLE users; --

Specific commands depend on your environment, but example SQL injection test commands might include sending crafted API requests or modifying configuration files with suspicious table_prefix values and monitoring for errors or unexpected database behavior.

Useful 0 Not Useful 0

Mitigation Strategies

The immediate mitigation step is to upgrade PraisonAI to version 4.6.9 or later and praisonaiagents to version 1.6.9 or later, where the vulnerability has been patched.

Until upgrading, avoid using externally controlled or user-editable values for the table_prefix and schema parameters in the affected backends.

Implement input validation and sanitization for all parameters passed into SQL queries, especially table_prefix and schema, to prevent injection.

Review your deployment for any custom or multi-tenant configurations that might pass unvalidated inputs into SQL queries and restrict or sanitize those inputs.

Useful 0 Not Useful 0

Compliance Impact

This SQL injection vulnerability in PraisonAI affects the confidentiality and integrity of data by allowing attackers to execute arbitrary SQL commands, potentially leading to unauthorized read, write, and deletion of sensitive information.

Such unauthorized access and manipulation of data can result in non-compliance with common standards and regulations like GDPR and HIPAA, which mandate strict controls over data privacy, integrity, and protection against unauthorized access.

Therefore, if exploited, this vulnerability could lead to breaches of personal or protected health information, violating regulatory requirements and potentially resulting in legal and financial consequences for affected organizations.

Useful 0 Not Useful 0