CVE-2026-60090: PraisonAI before 4.6.78 SQL/CQL Injection via vector dimension
PraisonAI before 4.6.78 fails to validate the caller-controlled dimension argument in the PGVector and Cassandra knowledge-store create_collection() backends. Although schema, keyspace, and collection-name identifiers are validated, the dimension value (declared as int but not enforced at runtime) is interpolated directly into the vector column of the generated CREATE TABLE DDL. A caller able to influence collection-creation dimensions can pass a string such as '3); DROP TABLE tenant_secrets; --' to inject SQL/CQL tokens into the statement executed by the database driver.
Security readout for executives and security teams
Plain-English summary
PraisonAI versions before 4.6.78 can let an attacker manipulate a vector “dimension” value during collection creation. If exposed, this could alter database commands against PGVector or Cassandra-backed knowledge stores, risking data theft, corruption, or service disruption.
Executive priority
Treat as urgent for PraisonAI deployments using PGVector or Cassandra where collection creation is reachable. The vulnerability can affect confidentiality, integrity, and availability of backing databases. Prioritize patching and access restriction.
Technical view
CVE-2026-60090 is CWE-89 SQL/CQL injection in PraisonAI create_collection() logic for PGVector and Cassandra knowledge-store backends. The dimension argument is declared as an integer but not enforced at runtime and is interpolated into generated CREATE TABLE DDL. CVSS 3.1 is 9.8: network, low complexity, no privileges, no user interaction.
Likely exposure
Highest exposure exists where untrusted users, tenants, agents, or API clients can influence knowledge-store collection creation dimensions in PraisonAI before 4.6.78 using PGVector or Cassandra backends.
Exploitation context
The provided sources describe a caller-controlled injection path and critical CVSS score. They do not show known active exploitation, and the CVE is not marked KEV in the supplied data.
Researcher notes
Evidence is limited to the CVE record, GitHub advisory, patch reference, and VulnCheck advisory. The issue is specifically the dimension value in generated DDL, despite validation of schema, keyspace, and collection names. No public exploitation evidence is provided in the supplied sources.
Mitigation direction
Upgrade PraisonAI to 4.6.78 or later per the advisory.
Restrict collection-creation capability to trusted administrators until patched.
Ensure dimension values are strictly validated as integers before use.
Review vendor advisory and patch commit for implementation details.
Validation and detection
Inventory PraisonAI deployments and confirm versions are below or at least 4.6.78.
Identify use of PGVector or Cassandra knowledge-store backends.
Check whether external users or tenants can influence collection dimensions.
Confirm patched code enforces integer dimension handling.
Review database audit logs for unexpected collection or table DDL activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.