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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-44337: 0.22% estimated exploitation activity in the next 30 days; percentile 12.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details This issue affects the public persistence layer exported by persistence/init.py, which exposes KnowledgeStore and createknowledgestore(). The factory wires the affected backends as supported knowledge-store providers in persistence/factory.py: - pgvector at persistence/factory.py - cassandra at persistence/factory.py - singlestorevector at persistence/factory.py The common root cause is that the KnowledgeStore interface accepts free-form collection names in createcollection(),…

Published by the source

11 May 2026, 13:57 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-3643-7v76-5cj2

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-3643-7v76-5cj2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44337

Advisory: PraisonAI knowledge-store backends interpolate unvalidated collection names into SQL and CQL queries
IDs: CVE-2026-44337, GHSA-3643-7v76-5cj2
Record: https://patchnext.com/advisories/cve-2026-44337 (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: praisonai 4.6.34. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI praisonai: affected >= 2.4.1, <= 4.6.33; fixed in 4.6.34

## Suggested inspection (read-only)
- `python -m pip show praisonai`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on praisonai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3643-7v76-5cj2 (OSV record GHSA-3643-7v76-5cj2 lists affected ranges: PyPI praisonai >=2.4.1 <4.6.34 (fixed))
- Verified: https://github.com/advisories/GHSA-3643-7v76-5cj2 (GitHub-reviewed advisory GHSA-3643-7v76-5cj2 lists affected ranges: PyPI praisonai >=2.4.1 <=4.6.33)

Commands are suggestions: review each one before running it.