dbcve.org
PraisonaiApplication · Praison

CVE-2026-34934

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-03
Fix available
A fix is available. Upgrade to 4.5.90 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
PraisonAI is a multi-agent teams system. Prior to version 4.5.90, 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. This issue has been patched in version 4.5.90.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PraisonAI versions before 4.5.90 contain a stored SQL injection vulnerability in the get_all_user_threads function. The function uses f-strings to construct raw SQL queries with thread IDs retrieved from the database, which are not escaped before inclusion in the query. An attacker can store a malicious payload as a thread ID via update_thread, which then executes when the application loads the thread list, granting full database access.

MitigationUpgrade to PraisonAI version 4.5.90 or later, which implements proper query parameterization. If immediate patching is not feasible, implement input validation on thread IDs and refactor queries to use parameterized statements instead of f-string concatenation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PraisonaiApplication
Affected:< 4.5.90

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed PraisonAI version
    Run 'pip show praisonai' or 'pip list | grep praisonai' to see the installed version
    Affected if Version is lower than 4.5.90
  2. Locate get_all_user_threads function
    Search the codebase for 'def get_all_user_threads' in Python files
    Affected if Function exists and uses f-strings for SQL query construction with thread_id parameter
  3. Inspect SQL query construction in get_all_user_threads
    Open the file containing get_all_user_threads and examine if f-strings or string concatenation are used with thread_id in raw SQL queries
    Affected if SQL queries are built using f-strings or string formatting without parameterized queries
  4. Check update_thread function for stored injection
    Search for 'def update_thread' and examine how thread_id values are stored to the database
    Affected if update_thread accepts and stores thread_id without sanitization
  5. Verify database query library usage
    Check if the application uses raw SQL with string formatting instead of parameterized queries or an ORM
    Affected if Code uses execute() or cursor with f-string/raw string SQL queries instead of parameterized statements

A user is affected if running PraisonAI version below 4.5.90 AND the codebase contains the vulnerable get_all_user_threads function using unsafe f-string SQL queries with thread IDs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.5.90 or later
Fixed in 4.5.90
Interim mitigation

Upgrade to PraisonAI version 4.5.90 or later, which implements proper query parameterization. If immediate patching is not feasible, implement input validation on thread IDs and refactor queries to use parameterized statements instead of f-string concatenation.

Recommended fix High confidence

Upgrade to PraisonAI version 4.5.90 or later

  1. Check the currently installed version of PraisonAI using: pip show praisonai or pip list | grep praisonai
  2. Upgrade PraisonAI to version 4.5.90 or later using: pip install --upgrade praisonai==4.5.90 (or pip install --upgrade praisonai to get the latest version)
  3. Verify the upgrade was successful by running: pip show praisonai and confirming the version number is 4.5.90 or higher
  4. Test the application to ensure the get_all_user_threads and update_thread functions work correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Praisonai Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34934 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34934 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data