Advisory record · GHSA-9cq8-3v94-434g

PraisonAI Has Second-Order SQL Injection in `get_all_user_threads`

CVSS 9.8 CriticalCriticalEPSS 0.0054 · 46th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 29 Jun 2026, 11:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
praisonaiPyPI<4.5.904.5.90
Identifiers
GHSA-9cq8-3v94-434g · CVE-2026-34934 · PYSEC-2026-470
Weakness (CWE)
CWE-89
Published
29 Jun 2026
Updated
13 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

PraisonAI versions before 4.5.90 are vulnerable to a second-order SQL injection in the get_all_user_threads function, which builds raw SQL from thread IDs read back from the database. An attacker who can store a crafted thread ID through update_thread could then run arbitrary SQL when the thread list loads, gaining access to sensitive data and the ability to modify or delete database contents. Upgrade praisonai to version 4.5.90 or later.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0054, the 46th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:04 UTC First seen by agentprime
  2. 31 Oct 2026, 15:04 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.