External risk intelligence

PraisonAI SQL Injection Vulnerability Allows Full Database Access.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-34934

PraisonAI is a multi-agent system designed as a web-based application or service. Such applications typically operate as internet-facing web interfaces or API endpoints to facilitate user interaction and thread management, making the vulnerable component commonly reachable from the public internet in standard deployment patterns.

SQL Injection

Praisonai

before 4.5.90

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a critical vulnerability in the PraisonAI multi-agent system, specifically impacting its ability to manage user threads. The flaw allows unauthenticated attackers to execute arbitrary SQL commands, potentially leading to a complete compromise of the system's database. This issue has been resolved in version 4.5.90.

  • Flaw allows unauthorized database access.
  • Critical vulnerability in multi-agent thread management.
  • Confirm exposure and ensure system is updated.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by first submitting a specially crafted thread ID to the system. When the application later retrieves and displays a list of threads, it uses the malicious ID to execute arbitrary SQL commands, giving the attacker full control over the database.

  • Unauthenticated network access required.
  • Malicious thread ID injection.
  • Full database compromise.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to gain full access to the PraisonAI system's database. When a user's thread list is loaded, an injected SQL query executes, potentially exposing or modifying all stored information.

  • Database contents at risk.
  • SQL injection via thread ID.
  • Full database access granted.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts PraisonAI, a multi-agent system. Given its function, application owners and platform teams are likely responsible for managing this technology. The first practical step is to identify all instances of PraisonAI, confirm their exposure and criticality, and then assign ownership to plan remediation.

  • Application owners should take ownership.
  • Verify PraisonAI deployment and reachability.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is PraisonAI?

PraisonAI is a framework used to build and orchestrate multi-agent systems. It allows developers to coordinate teams of AI agents to perform complex tasks. By managing various user interactions through thread systems, it acts as a backend service that often powers web-based applications where users initiate and track multi-agent processes.

What is the vulnerability in CVE-2026-34934?

This vulnerability is an instance of Improper Neutralization of Special Elements used in an SQL Command, classified as CWE-89. It means the software takes user-provided data and incorporates it directly into database queries without proper sanitization. In this case, malicious input disguised as a thread ID is interpreted as a command, allowing the database to execute unintended instructions from an outside source.

How does an attacker trigger this SQL injection?

An attacker triggers the flaw by submitting a crafted, malicious thread ID to the system. The vulnerability is not triggered by simply visiting the site; the malicious payload must be stored in the database first. The SQL injection occurs later when the application retrieves the stored thread list to display it, causing the system to execute the injected code.

Is my PraisonAI instance at risk?

According to Halo Surface Signal, PraisonAI is typically deployed as a web-facing service or API to support user interaction, meaning the affected components are often reachable from the public internet. If your instance is accessible to the public, it faces a higher likelihood of being reachable by unauthorized users who could attempt to inject malicious thread IDs.

How do I secure my PraisonAI deployment?

The primary response is to update your software to version 4.5.90 or later, as this release contains the fix that correctly sanitizes thread ID inputs. Start by inventorying all systems running PraisonAI to identify which versions are outdated. Prioritize patching any instances that are reachable over the network to prevent potential unauthorized database access.

References