CVE-2026-40315 MervinPraison CVE debrief

Who should care

Defenders responsible for PraisonAI deployments should assess exposure and prioritize verification and remediation efforts, reviewing configuration inputs for potential SQL injection vulnerabilities. This includes operators, platform administrators, vulnerability management teams, and security teams who need to ensure the security and integrity of PraisonAI deployments.

Why it matters

CVE-2026-40315 is an SQL identifier injection vulnerability in PraisonAI's SQLiteConversationStore. Defenders should prioritize verifying and upgrading to PraisonAI version 4.5.133 or later, and review configuration inputs for potential SQL injection vulnerabilities.

• Potential unauthorized data access
• Query result tampering through SQL injection
• Internal schema disclosure through SQL injection
• Verification of configuration inputs for potential SQL injection vulnerabilities

Technical summary

The vulnerability is caused by the direct concatenation of the table_prefix configuration value into SQL queries without validation or sanitization. This allows an attacker to inject arbitrary SQL fragments and alter query structure, enabling unauthorized data access and query result tampering. The vulnerability propagates from configuration input in config.py, through factory.py, to the SQL query construction in sqlite.py. Exploitation requires the ability to influence configuration input, and successful exploitation leads to internal schema disclosure and full query result tampering.

Defensive priority

Defenders should prioritize verifying and upgrading to PraisonAI version 4.5.133 or later, and review configuration inputs for potential SQL injection vulnerabilities.

Recommended defensive actions

• Verify and upgrade to PraisonAI version 4.5.133 or later
• Review configuration inputs for potential SQL injection vulnerabilities
• Monitor for unauthorized data access and query result tampering
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability is caused by the direct concatenation of the table_prefix configuration value into SQL queries without validation or sanitization. This allows an attacker to inject arbitrary SQL fragments and alter query structure.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.