Dify before 1.16.0-rc1 contains a SQL injection vulnerability in the MyScale vector store backend that allows attackers to execute arbitrary SQL by supplying unsanitized search parameters to the search_by_full_text method without escaping or parameterization. Attackers can inject malicious SQL through the search parameters to read, modify, or delete data in the underlying ClickHouse database.
CVE-2026-61461
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-10. the CNA's CVSS baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EPSS
- 27.9%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 14, 2026
Advisory Details (5)
Auto-updated Jul 10, 2026Dify < 1.16.0-rc1 SQL Injection via MyScale Vector Store search_by_full_text | Advisories | VulnCheck
https://www.vulncheck.com/advisories/dify-rc1-sql-injection-via-myscale-vector-store-search-by-full-textcommit d9884efaeea8 (langgenius/dify)
Fix landed in langgenius/dify commit d9884efaeea8 — awaiting tagged release
https://github.com/langgenius/dify/commit/d9884efaeea8322706e24c560d2c17e5bf3fab5ffix: sql injection
Fix merged in langgenius/dify PR #38295 on 2026-07-02 — awaiting tagged release
https://github.com/langgenius/dify/pull/38295SQL Injection in Dify MyScale Vector Store via `search_by_full_text` · Issue #38281 · langgenius/dify · GitHub
https://github.com/langgenius/dify/issues/38281v1.16.0-rc1
Patch available: langgenius/dify 1.16.0-rc1 (pre-release)
https://github.com/langgenius/dify/releases/tag/1.16.0-rc1Vendor Advisories for CVE-2026-61461(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 29× in last 7d / 29× 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.
- 2026-07-16 00:41 UTCEG score recompute
- 2026-07-16 00:41 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 12:04 UTCEG score recompute
- 2026-07-15 12:03 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 23:25 UTCEG score recompute
- 2026-07-14 23:24 UTCGHSA enrichment
- 2026-07-14 10:44 UTCEG score recompute
- 2026-07-14 10:44 UTCGHSA enrichment
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 22:06 UTCEG score recompute
- 2026-07-13 22:06 UTCGHSA enrichment
- 2026-07-13 09:29 UTCEG score recompute
- 2026-07-13 09:29 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 20:52 UTCEG score recompute
- 2026-07-12 20:52 UTCGHSA enrichment
- 2026-07-12 08:14 UTCEG score recompute
- 2026-07-12 08:14 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 19:37 UTCEG score recompute
- 2026-07-11 19:37 UTCGHSA enrichment
Show 4 moreShow fewer
- 2026-07-11 07:00 UTCEG score recompute
- 2026-07-11 07:00 UTCGHSA enrichment
- 2026-07-10 18:23 UTCEG score recompute
- 2026-07-10 18:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-61461?
When was CVE-2026-61461 disclosed?
Is CVE-2026-61461 actively exploited?
What is the CVSS score of CVE-2026-61461?
How do I remediate CVE-2026-61461?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-61461
Is Your Infrastructure Affected by CVE-2026-61461?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.