CVE-2026-60090

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-11. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
33.2%
KEV
Not listed

Published

July 11, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Jul 13, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic

PraisonAI before 4.6.78 SQL/CQL Injection via vector dimension | Advisories | VulnCheck

https://www.vulncheck.com/advisories/praisonai-before-sql-cql-injection-via-vector-dimension
github Patch Available🟡 PoC Available

PGVector and Cassandra knowledge stores interpolate vector dimensions into DDL · Advisory · MervinPraison/PraisonAI · GitHub

https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-wf65-4jjx-q444
github_commit Patch Available

commit 3aa9cbc2bd49 (MervinPraison/PraisonAI)

Patch available: MervinPraison/PraisonAI v4.6.115 (contains commit 3aa9cbc2bd49)

https://github.com/MervinPraison/PraisonAI/commit/3aa9cbc2bd49c23a32be0a89a5e620d13d843eab

Vendor Advisories for CVE-2026-60090(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 60× in last 7d / 60× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 23:48 UTCEG score recompute
  2. 2026-07-15 23:48 UTCGHSA enrichment
  3. 2026-07-15 19:44 UTCEG score recompute
  4. 2026-07-15 19:44 UTCGHSA enrichment
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 15:39 UTCEG score recompute
  7. 2026-07-15 15:39 UTCGHSA enrichment
  8. 2026-07-15 11:35 UTCEG score recompute
  9. 2026-07-15 11:35 UTCGHSA enrichment
  10. 2026-07-15 07:29 UTCEG score recompute
  11. 2026-07-15 07:29 UTCGHSA enrichment
  12. 2026-07-15 03:24 UTCEG score recompute
  13. 2026-07-15 03:24 UTCGHSA enrichment
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 23:20 UTCEG score recompute
  17. 2026-07-14 23:19 UTCGHSA enrichment
  18. 2026-07-14 19:13 UTCEG score recompute
  19. 2026-07-14 19:13 UTCGHSA enrichment
  20. 2026-07-14 15:07 UTCEG score recompute
  21. 2026-07-14 15:07 UTCGHSA enrichment
  22. 2026-07-14 11:01 UTCEG score recompute
  23. 2026-07-14 11:01 UTCGHSA enrichment
  24. 2026-07-14 06:52 UTCEG score recompute
  25. 2026-07-14 06:52 UTCGHSA enrichment
Show 35 more
  1. 2026-07-14 02:47 UTCEG score recompute
  2. 2026-07-14 02:46 UTCGHSA enrichment
  3. 2026-07-13 22:42 UTCEG score recompute
  4. 2026-07-13 22:42 UTCGHSA enrichment
  5. 2026-07-13 22:31 UTCEPSS rescore
  6. 2026-07-13 18:37 UTCEG score recompute
  7. 2026-07-13 18:37 UTCGHSA enrichment
  8. 2026-07-13 14:32 UTCEG score recompute
  9. 2026-07-13 14:32 UTCGHSA enrichment
  10. 2026-07-13 10:28 UTCEG score recompute
  11. 2026-07-13 10:28 UTCGHSA enrichment
  12. 2026-07-13 06:23 UTCEG score recompute
  13. 2026-07-13 06:23 UTCGHSA enrichment
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-13 02:16 UTCEG score recompute
  17. 2026-07-13 02:16 UTCGHSA enrichment
  18. 2026-07-12 22:11 UTCEG score recompute
  19. 2026-07-12 22:11 UTCGHSA enrichment
  20. 2026-07-12 18:07 UTCEG score recompute
  21. 2026-07-12 18:07 UTCGHSA enrichment
  22. 2026-07-12 14:03 UTCEG score recompute
  23. 2026-07-12 14:02 UTCGHSA enrichment
  24. 2026-07-12 09:56 UTCEG score recompute
  25. 2026-07-12 09:56 UTCGHSA enrichment
  26. 2026-07-12 05:51 UTCEG score recompute
  27. 2026-07-12 05:51 UTCGHSA enrichment
  28. 2026-07-12 01:46 UTCEG score recompute
  29. 2026-07-12 01:46 UTCGHSA enrichment
  30. 2026-07-11 21:41 UTCEG score recompute
  31. 2026-07-11 21:41 UTCGHSA enrichment
  32. 2026-07-11 17:37 UTCEG score recompute
  33. 2026-07-11 17:37 UTCGHSA enrichment
  34. 2026-07-11 13:33 UTCEG score recompute
  35. 2026-07-11 13:32 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-60090?
CVE-2026-60090 is a critical vulnerability published on July 11, 2026. PraisonAI before 4.6.78 fails to validate the caller-controlled dimension argument in the PGVector and Cassandra knowledge-store createcollection() backends. Although schema, keyspace, and collection-name identifiers are validated, the dimension value (declared as int but not enforced at runtime)…
When was CVE-2026-60090 disclosed?
CVE-2026-60090 was first published in the National Vulnerability Database on July 11, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-60090 actively exploited?
CVE-2026-60090 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-60090?
CVE-2026-60090 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-60090?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-60090, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-60090

Explore →

Is Your Infrastructure Affected by CVE-2026-60090?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs