CVE-2026-34934 MervinPraison CVE debrief

Who should care

Users of PraisonAI versions prior to 4.5.90 should apply the patch to prevent exploitation. This includes operators, administrators, and security teams responsible for managing PraisonAI deployments. The vulnerability can lead to full database access, which can have significant impacts on confidentiality, integrity, and availability. Defenders should review their systems and apply patches or mitigations as needed.

Technical summary

The get_all_user_threads function in PraisonAI constructs raw SQL queries using f-strings with unescaped thread IDs fetched from the database. This allows an attacker to store a malicious thread ID via update_thread, leading to full database access when the application loads the thread list. The issue has been patched in version 4.5.90. Users of PraisonAI should review their deployments and apply the patch to prevent exploitation. The vulnerability has a CVSS score of 9.8 and is considered critical.

Defensive priority

High

Recommended defensive actions

• Apply the patch to upgrade to version 4.5.90 or later
• Review and sanitize user input to prevent SQL injection
• Monitor database activity for suspicious queries
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD detail provide information on the vulnerability and its patch. The vendor advisory on GitHub provides additional context on the issue. Evidence is limited to public sources and may not reflect the full scope or impact of the vulnerability. Defenders should verify affected systems and apply patches or mitigations as needed. The vulnerability allows an attacker to store a malicious thread ID via update_thread, leading to full database access when the application loads the thread list. Users should review and sanitize user input to prevent SQL injection and monitor database activity for suspicious queries.

Official resources