CVE-2026-34934 — AI Deep Analysis Summary

Q: What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: SQL Injection in PraisonAI. 💥 **Consequences**: Attackers can bypass security controls and gain full access to the underlying database. Critical integrity and confidentiality loss.

Q: Root Cause? (CWE/Flaw)

🛡️ **CWE**: CWE-89 (SQL Injection). 🔍 **Flaw**: The `get_all_user_threads` function constructs raw SQL queries using **unescaped thread IDs**. No input validation or parameterization is used.

Q: Who is affected? (Versions/Components)

📦 **Vendor**: MervinPraison. 📉 **Affected**: PraisonAI versions **prior to 4.5.90**. If you are running an older version, you are vulnerable.

Q: What can hackers do? (Privileges/Data)

💀 **Privileges**: Full Database Access. 📂 **Data**: Attackers can read, modify, or delete any data in the database. This includes user threads and potentially sensitive application data.

Q: Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: **LOW**. 🔑 **Auth**: PR:N (Privileges Required: None). 🌐 **Network**: AV:N (Network Vector). 👀 **UI**: UI:N (User Interaction: None). 📝 **AC**: AC:L (Attack Complexity: Low).

Q: Is there a public Exp? (PoC/Wild Exploitation)

🚫 **Public Exp**: **No**. 📄 **PoC**: The `pocs` field is empty. 🔗 **Ref**: GitHub Advisory exists (GHSA-9cq8-3v94-434g), but no public exploit code is currently available.

Q: How to self-check? (Features/Scanning)

🔍 **Self-Check**: Scan for PraisonAI instances. 🧪 **Test**: Look for the `get_all_user_threads` endpoint. ⚠️ **Indicator**: Check if thread IDs are passed directly into SQL queries without sanitization.

Q: Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: **Yes**. 🔧 **Patch**: Upgrade PraisonAI to version **4.5.90** or later. 📢 **Source**: Official GitHub Security Advisory.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. 📊 **CVSS**: 9.8 (Critical). 🚀 **Priority**: Patch immediately. The vulnerability is easy to exploit and has severe consequences (Full DB Access).

Updated May 06, 2026 CVSS 9.8 · Critical

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: SQL Injection in PraisonAI. <br>💥 **Consequences**: Attackers can bypass security controls and gain full access to the underlying database. Critical integrity and confidentiality loss.

Q2Root Cause? (CWE/Flaw)

🛡️ **CWE**: CWE-89 (SQL Injection). <br>🔍 **Flaw**: The `get_all_user_threads` function constructs raw SQL queries using **unescaped thread IDs**. No input validation or parameterization is used.

Q3Who is affected? (Versions/Components)

📦 **Vendor**: MervinPraison. <br>📉 **Affected**: PraisonAI versions **prior to 4.5.90**. If you are running an older version, you are vulnerable.

Q4What can hackers do? (Privileges/Data)

💀 **Privileges**: Full Database Access. <br>📂 **Data**: Attackers can read, modify, or delete any data in the database. This includes user threads and potentially sensitive application data.

Q5Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: **LOW**. <br>🔑 **Auth**: PR:N (Privileges Required: None). <br>🌐 **Network**: AV:N (Network Vector). <br>👀 **UI**: UI:N (User Interaction: None). <br>📝 **AC**: AC:L (Attack Complexity: Low).

Q6Is there a public Exp? (PoC/Wild Exploitation)

🚫 **Public Exp**: **No**. <br>📄 **PoC**: The `pocs` field is empty. <br>🔗 **Ref**: GitHub Advisory exists (GHSA-9cq8-3v94-434g), but no public exploit code is currently available.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: Scan for PraisonAI instances. <br>🧪 **Test**: Look for the `get_all_user_threads` endpoint. <br>⚠️ **Indicator**: Check if thread IDs are passed directly into SQL queries without sanitization.

Q8Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: **Yes**. <br>🔧 **Patch**: Upgrade PraisonAI to version **4.5.90** or later. <br>📢 **Source**: Official GitHub Security Advisory.

Q9What if no patch? (Workaround)

🛡️ **Workaround**: If you cannot upgrade immediately: <br>1. Implement strict input validation on thread IDs. <br>2. Use parameterized queries instead of string concatenation. <br>3.…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. <br>📊 **CVSS**: 9.8 (Critical). <br>🚀 **Priority**: Patch immediately. The vulnerability is easy to exploit and has severe consequences (Full DB Access).

Continue exploring

Vulnerability detail Full AI analysis (login) MervinPraison CWE-89