CVE-2026-60090

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Elevated
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 11, 2026

Last Modified

July 14, 2026

Advisory Details (3)

Auto-updated Oct 11, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

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
Web page

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 commit Patch Available

commit 3aa9cbc2bd49 (MervinPraison/PraisonAI)

Patch available: MervinPraison/PraisonAI v4.6.149 (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.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
praisonai0.0.1 ... 4.6.9 (763 versions)
  • every version up to 4.6.78: fixed in 4.6.78
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 376 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 276 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 01:51 UTCEG score recompute
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  3. 2026-10-12 22:06 UTCEG score recompute
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  5. 2026-10-12 15:52 UTCEG score recompute
  6. 2026-10-11 19:36 UTCEG score recompute
  7. 2026-10-11 16:51 UTCEG score recompute
  8. 2026-10-11 14:13 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-10-01 14:53 UTCEG score recompute
  21. 2026-10-01 14:53 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-09-28 09:41 UTCEG score recompute
  25. 2026-09-28 09:41 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 75 more
  1. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  2. 2026-09-24 10:28 UTCEG score recompute
  3. 2026-09-24 10:28 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  5. 2026-09-23 09:44 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-09-23 05:40 UTCEG score recompute
  7. 2026-09-23 05:40 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  9. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  10. 2026-09-18 10:07 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-09-18 05:11 UTCEG score recompute
  12. 2026-09-18 05:11 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  16. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-09-14 07:48 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-09-14 03:41 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-09-13 23:37 UTCEG score recompute
  20. 2026-09-13 23:37 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  22. 2026-09-13 16:40 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-09-13 12:12 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-09-13 08:07 UTCEG score recompute
  25. 2026-09-13 08:07 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-09-12 13:31 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-09-12 02:21 UTCEG score recompute
  28. 2026-09-12 02:21 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  30. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  31. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  32. 2026-09-08 02:24 UTCEG score recompute
  33. 2026-09-08 02:24 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  35. 2026-09-06 13:54 UTCEG score recompute
  36. 2026-09-06 13:54 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  38. 2026-09-06 01:45 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-09-05 21:35 UTCEG score recompute
  40. 2026-09-05 21:35 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  42. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  43. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  44. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  45. 2026-08-31 00:39 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-08-30 20:33 UTCEG score recompute
  47. 2026-08-30 20:33 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  49. 2026-08-30 16:29 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-08-30 11:10 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-08-30 05:54 UTCEG score recompute
  52. 2026-08-30 05:54 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  54. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  55. 2026-08-28 02:37 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  56. 2026-08-27 21:38 UTCEG score recompute
  57. 2026-08-27 21:38 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  59. 2026-08-27 00:22 UTCEG score recompute
  60. 2026-08-27 00:21 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  62. 2026-08-26 12:53 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  63. 2026-08-26 08:06 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-08-26 02:44 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-08-25 13:55 UTCEG score recompute
  66. 2026-08-25 13:55 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  68. 2026-08-25 09:46 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-08-25 04:18 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-08-25 00:13 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-08-24 20:08 UTCEG score recompute
  72. 2026-08-24 20:08 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  73. 2026-08-24 13:27 UTCEG score recompute
  74. 2026-08-24 13:27 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8
  75. 2026-08-24 09:23 UTCGHSA enrichmentGHSA-q65p-7p84-495c · GitHub severity CRITICAL · GitHub CVSS 9.8

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-60090?
CVE-2026-60090 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2026-60090 was made public on June 25, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 11, 2026. EchelonGraph's copy of the record carries a last-modified date of July 14, 2026; the record at its source may have been updated since.
Is CVE-2026-60090 actively exploited?
CVE-2026-60090 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-60090?
CVE-2026-60090 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-60090?
A fix for CVE-2026-60090 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-60090 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs