langgenius dify up to 1.16.0 MyScale Vector Store Backend search_by_full_text sql injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in langgenius dify up to 1.16.0. The affected element is the function search_by_full_text of the component MyScale Vector Store Backend. This manipulation causes sql injection. This vulnerability is handled as CVE-2026-61461. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability has been found in langgenius dify up to 1.16.0 and classified as critical. Affected by this vulnerability is the function search_by_full_text of the component MyScale Vector Store Backend. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-61461 since 07/09/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

Upgrading to version 1.16.0-rc1 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• langgenius

Name

• dify

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16.0

Website

• Product: https://github.com/langgenius/dify/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion