CVE-2026-44337

PraisonAI knowledge-store backends interpolate unvalidated collection names into SQL and CQL queries

Published May 8, 2026 CVSS 3.1 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
PraisonAI is a multi-agent teams system. From version 2.4.1 to before version 4.6.34, PraisonAI exposes optional SQL/CQL-backed knowledge-store implementations that build table and index identifiers from unvalidated name and collection arguments. Applications that pass untrusted collection names into these backends can trigger SQL or CQL injection. This issue has been patched in version 4.6.34.

Analysis

AI-generated

Technical impact

PraisonAI implements optional SQL and CQL backends for its knowledge store. From version 2.4.1 up to just before 4.6.34, the system builds table and index identifiers directly from the collection name supplied by the application. This allows an attacker to supply an untrusted collection name that contains injected SQL or CQL code, enabling exploitation of CWE-20 and CWE-89 weaknesses. The injection can lead to unauthorized data disclosure, alteration, or destruction within the database hierarchy, impacting the confidentiality, integrity, and availability of the knowledge store.

Affected Systems

Vendors affected: MervinPraison, product: PraisonAI. Versions vulnerable include all releases from 2.4.1 through the latest pre‑4.6.34. Products after 4.6.34 contain the fix.

Risk and Exploitability

The CVSS score of 6.3 indicates a moderate severity. EPSS data is unavailable, and the vulnerability is not listed in CISA’s KEV catalog, suggesting no currently known widespread exploitation. The likely attack vector requires an attacker to interact with an application that uses the SQL/CQL knowledge‑store and control the collection name parameter; therefore, the vulnerability is accessible via the application layer and may require authentication or elevated permissions to exploit fully. External exploitation would be possible if the application is exposed over a network and accepts uncontrolled collection names.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the official patch delivered in PraisonAI 4.6.34 or later.
  • If patch deployment is delayed, sanitize and validate all collection name inputs before they are used in SQL/CQL statements, or use parameterized queries that avoid dynamic identifier construction.
  • Disable the optional SQL or CQL backends entirely for environments that do not require them, and enforce least‑privilege database roles on the remaining services.

Generated by OpenCVE AI on May 8, 2026 at 18:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-3643-7v76-5cj2 PraisonAI knowledge-store backends interpolate unvalidated collection names into SQL and CQL queries
History
Type Values Removed Values Added
First Time appeared Praison
Praison praisonai
CPEs cpe:2.3:a:praison:praisonai:*:*:*:*:*:*:*:*
Vendors & Products Praison
Praison praisonai
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description PraisonAI is a multi-agent teams system. From version 2.4.1 to before version 4.6.34, PraisonAI exposes optional SQL/CQL-backed knowledge-store implementations that build table and index identifiers from unvalidated name and collection arguments. Applications that pass untrusted collection names into these backends can trigger SQL or CQL injection. This issue has been patched in version 4.6.34.
Title PraisonAI knowledge-store backends interpolate unvalidated collection names into SQL and CQL queries
Weaknesses CWE-20
CWE-89
References
Metrics cvssV3_1

{'score': 6.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L'}

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
May 8, 2026, 2:19 PM
Reserved
May 5, 2026, 7:52 PM
Status
Analyzed
Published
May 8, 2026, 2:16 PM
Modified
Jun 17, 2026, 10:50 AM