CVE-2026-60090 — PraisonAI before 4.6.78 fails to validate the caller-controlled…
CVE-2026-60090 — PraisonAI before 4.6.78 fails to validate the caller-controlled… has a recently disclosed critical-severity vulnerability (CVE-2026-60090). It has not been reported as actively exploited — patch it proactively as part of your normal cycle before that changes.
What is this vulnerability?
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.
How it works
This is classified as SQL Injection. In plain terms, an attacker could use this flaw in the affected product to gain access, disrupt service, or steal data — the exact impact depends on how it’s deployed in your environment.
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigations
- Apply the vendor’s security patch or update as soon as it’s available and tested.
- If no patch exists yet, apply the vendor’s temporary workaround.
- Limit network exposure of the affected system until it’s patched.
- Track the vendor advisory — disclosed vulnerabilities can move to active exploitation quickly.
Recommendations
- Confirm whether this vendor’s affected product is used anywhere in your environment.
- Patch internet-facing systems first, then internal ones.
- Prioritise by exposure and exploitability while a fix is scheduled.
- Subscribe to the vendor’s security advisories for earlier warning next time.
Compiled from the National Vulnerability Database (NVD), referenced in 3 public advisories. Listed as recently disclosed — not confirmed exploited.