# CVE-2026-61461: Dify < 1.16.0-rc1 SQL Injection via MyScale Vector Store search_by_full_text

> Attackers can execute arbitrary SQL commands via unsanitized search parameters in the MyScale vector store, allowing data access and modification.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-hw83-q5rh-7hgf

## What is CVE-2026-61461?

CVE-2026-61461 is a high-severity SQL injection vulnerability in langgenius dify, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-61461?

It affects 1 product.


Products: Dify Dify.

## How do I fix CVE-2026-61461?

No fix has been published for CVE-2026-61461 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-61461 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61461 exists.

## Other vulnerabilities in langgenius dify

- [CVE-2026-41947](https://insights.sbomify.com/CVE-2026-41947/): Dify < 1.14.2 Authorization Bypass via Trace Configuration Endpoints (critical 9.3)
- [CVE-2026-41948](https://insights.sbomify.com/CVE-2026-41948/): Dify v1.14.1 Path Traversal via Plugin Daemon Internal API Access (critical 9.3)
- [CVE-2025-0185](https://insights.sbomify.com/CVE-2025-0185/): Pandas Query Injection in langgenius/dify (high 8.8)
- [CVE-2025-67732](https://insights.sbomify.com/CVE-2025-67732/): Dify Vulnerable to Plaintext API Key Exposure via Model Provider Configuration Endpoint (high 8.4)
- [CVE-2026-41949](https://insights.sbomify.com/CVE-2026-41949/): Dify < 1.14.2 Authorization Bypass via File Preview Endpoint (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61461 and fix it if it is affected.

What it is: CVE-2026-61461 is a high-severity SQL injection vulnerability in langgenius dify, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61461 exists.

Affected product: langgenius dify. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61461/ (Markdown: https://insights.sbomify.com/CVE-2026-61461/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61461
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61461
- OSV: https://osv.dev/vulnerability/CVE-2026-61461

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61461/
Summaries are generated and may contain mistakes; the official description above is the record.