dbcve.org
DifyApplication

CVE-2026-61461

HIGH · 8.8 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 1.16.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in Dify's MyScale vector store backend (versions before 1.16.0-rc1) allows attackers to execute arbitrary SQL commands through unsanitized search parameters in the search_by_full_text method without proper escaping or parameterization, enabling read, modify, or delete operations on the underlying ClickHouse database.

MitigationUpgrade Dify to version 1.16.0-rc1 or later which implements proper input sanitization and query parameterization for the MyScale vector store search methods.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DifyApplication
Affected:< 1.16.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Dify version
    Check the Dify version running in your environment (typically via container tags, deployment manifests, or the Dify admin panel)
    Affected if The installed version is below 1.16.0-rc1 (versions 1.16.0 and earlier are affected)
  2. Confirm MyScale vector store is in use
    Review your Dify vector store configuration to verify MyScale is configured as the backend vector database
    Affected if MyScale is configured and actively used as the vector store for your Dify installation
  3. Verify search_by_full_text method exposure
    Check if the MyScale vector store search functionality is exposed through Dify's API or UI endpoints that accept search query parameters
    Affected if Users or applications can invoke the search_by_full_text method with custom parameters against the MyScale backend
  4. Inspect ClickHouse database access
    Review database connection logs or audit records for unexpected SQL queries originating from the Dify application to the ClickHouse database
    Affected if Unusual or unsanitized SQL patterns appear in ClickHouse query logs stemming from Dify MyScale operations

You are affected if your Dify version is below 1.16.0-rc1 AND you use MyScale as your vector store backend with the search_by_full_text method exposed to untrusted input.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.16.0 or later
Fixed in 1.16.0
Vendor patch github.com →
Interim mitigation

Upgrade Dify to version 1.16.0-rc1 or later which implements proper input sanitization and query parameterization for the MyScale vector store search methods.

Recommended fix High confidence

1.16.0-rc1

  1. 1. Identify all Dify deployments running versions prior to 1.16.0-rc1.
  2. 2. Review the Dify deployment for usage of the MyScale vector store backend.
  3. 3. If using MyScale vector store, note that search parameters in search_by_full_text are not sanitized and can allow SQL injection.
  4. 4. Plan an upgrade to Dify version 1.16.0-rc1 or later.
  5. 5. Before upgrading in production, test the upgrade in a staging environment to verify functionality.
  6. 6. Perform the upgrade following Dify's standard upgrade procedure.
  7. 7. After upgrading, verify that the MyScale vector store search functionality works correctly with the fix applied.
Caveat Review release notes for 1.16.0-rc1 to check for any breaking changes from your current version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dify Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-61461 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-61461 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data